Supported Formats & Upload Limits

Every file format CartaX supports and the current size limits — point clouds, orthophotos, DEMs, vectors, 3D models and 360° data in one table.

2026-07-17 · 3 min read

This page lists everything you can upload to CartaX and the limits that apply, in a single table. Other guides link here for size/limit facts; when limits change, this page is updated first.

Summary table

Data type Formats Upper limit Processing
Point cloud (raw) LAS, LAZ 5 GB / 150 million points Cloud conversion (tokens)
Point cloud (ready octree) Potree octree folder Your storage quota Direct registration, token-free
Orthophoto (raw) GeoTIFF (.tif/.tiff) 3 GB / ~1.5 gigapixels COG conversion (tokens)
Orthophoto (ready COG) Cloud Optimized GeoTIFF Your storage quota Auto-detected, token-free
Orthophoto (tile package) XYZ (z/x/y) PNG-JPEG folder 2 GB Direct registration
Elevation model DSM / DTM GeoTIFF 2 GB Pairs with your orthophoto; elevation & profile queries
Vector GeoJSON 100 MB / 250,000 features Processed in the browser
Vector KML / KMZ 50 MB / 150,000 features Processed in the browser
Vector Shapefile (.zip) 250 MB / 250,000 features Processed in the browser
Vector (CAD) DXF 40 MB / 25,000 entities Processed in the browser
3D model 3D Tiles (tileset.json + b3dm) Your storage quota Direct registration
3D model GLB / glTF 2 GB Placed on the map
360° collection Panorama photos (+ position table) 5 GB (single image 64 MB) Direct upload
360° video Equirectangular MP4 5 GB / up to 8K Uploaded to streaming infrastructure

Point clouds: LAS/LAZ and ready octrees

Raw LAS/LAZ files are converted in the cloud to a browser-friendly octree format; conversion uses processing tokens and is limited to 5 GB / 150 million points per file. For larger datasets you have two options:

  • Split the data and upload it as multiple layers.
  • Convert to an octree on your desktop and upload it as a "ready octree" — this path is token-free and only subject to your storage quota.

More detail: What are LAS and LAZ files?

Orthophotos: GeoTIFF, COG and tile packages

Raw GeoTIFFs are accepted up to 3 GB and ~1.5 gigapixels and converted to COG in the cloud (tokens). If your file is already a COG, it is auto-detected and registered token-free. You can also upload z/x/y tile folders produced by drone software directly (up to 2 GB).

Elevation models (DSM/DTM)

You can add a DSM/DTM GeoTIFF (up to 2 GB) alongside your orthophoto; elevation readouts, profiles and volume measurements use this model.

Vectors and CAD

GeoJSON, KML/KMZ, Shapefile (zip) and DXF files are processed entirely in the browser — your data is drawn straight onto your map without a processing round-trip to a server. The feature-count limits in the table keep the map fluid.

360° panoramas and video

Panorama collections (photos + an optional JSON/CSV/Excel position table) upload up to 5 GB in total; positions are read from EXIF first. 360° videos are supported up to 5 GB and 8K; videos over 200 MB are sent with resumable chunked upload. For GPS synchronization, DJI .SRT or .GPX sidecar files (Insta360, GoPro, Ricoh) are used.

Common questions

My file exceeds a limit — what now? For point clouds the ready-octree path, and for orthophotos the ready-COG path, allow much larger data within your storage quota. CartaX Studio makes those conversions easy on your own machine.

What is a token? A monthly processing allowance used by cloud conversions; see pricing for plan details.