Status: app version v26.11.250.0

Memory and file size limits

What the app and the browser can handle, how big files get and what CAD programs can still process. All numbers come from measurements or are fixed limits of the app.

Topic Limit and recommendation
Browser tabThe app runs entirely in the browser. A tab only gets limited memory (in Chrome usually a few GB), a single data array at most 2 GiB, a single string about 512 MiB. If a limit is exceeded, the browser ends the tab (“Aw, Snap!”, error code 5). That is why the app reads and writes large files in pieces and refuses calculations that would not fit up front, instead of showing half a result.
Loading a point cloudA cloud keeps its coordinates in one data array; this sets the maximum of 178,956,970 points per cloud. Uncompressed .las files over 2 GiB are read in slices; if the point count exceeds the maximum, the app offers to thin the file before loading. LAZ that would unpack to 1 GiB or more takes a memory-saving path. A live preview shows large files while they are still loading.
Classic and OctreeClassic draws every point of the cloud in every frame — simple and complete, but the frame rate drops with the point count. Octree splits the cloud into tiles and draws only what is in view, dense nearby and thinned in the distance (at rest up to 24 million points, while moving up to 12 million); for that it needs its own tile memory (default 1536 MB) and a moment to build the tiles. The automatic setting uses Classic up to 30 million points and Octree above (Settings → Display, limit adjustable from 1 to 500 million). Measuring, sections, DGM and exports always use the full cloud in both modes — the mode only affects the display.
Contour linesThe count happens before the calculation. Above 3,000,000 line pieces nothing is created, and the status line names the smallest interval that fits. Below that, the calculation runs in sections with preview and progress. Example dyke terrain (845 × 541 m, DGM 0.4 m) at 0.1 m interval: 1.35 million line pieces, 5.36 million points after smoothing.
Exporting contour linesDXF is a text file in which every vertex takes up several lines. The dyke example (0.1 m interval, 1.34 million points without smoothing) produces these file sizes: 2D polyline (height as elevation): about 55 MB 3D polyline: about 180 MB — the 3D version carries no extra information, because a contour line has the same height everywhere. 3D points only as DXF: about 150 MB, because every point is its own object with handle and layer. 3D points only as an XYZ or CSV file: about 40 MB. With smoothing there are four times as many points (5.34 million) and the files grow accordingly: about 210 / 700 / 600 / 160 MB. If you only need points for a volume calculation, use XYZ or CSV without smoothing. The app writes each of these files in pieces so the tab does not crash.
Import: load lineThe DXF and GeoJSON import dialog shows below the table, for the current selection: shapes, vertices, estimated memory (150 bytes per vertex plus 7.5 KB per shape) and the approximate size of a later DXF export (134 bytes per vertex); both are measured approximations. From one million vertices or 1 GB estimated memory the line turns yellow: display and export become sluggish. The import is never blocked — deselecting layers or types helps.
Limits in CAD programsCAD programs usually read a DXF completely and keep every vertex as its own object; files of a few hundred MB open slowly or not at all, and working in them gets sluggish. For deliveries: 2D polyline instead of 3D polyline, vertex POINTs only when needed, the interval as coarse as the job allows, crop the area with a boundary or section box, and split large areas into several files. Point clouds do not belong in DXF — use LAS/LAZ for them (AutoCAD reads them via ReCap, for example).
Point cloud exportLAS is written in pieces of 4 million points, each piece goes straight into the file — the size is limited only by memory and disk. Rule of thumb: LAS 1.2 needs 34 bytes per point (100 million points ≈ 3.2 GB), lossless LAZ about 12–30% of that, compressed in the background as a stream. Thinning to a point spacing, cropping to a boundary or section box, and LAZ make the export smaller. With two clouds, both are merged before thinning; that temporarily needs room for both.
Memory display in the footerThe footer shows “Memory ≈ …”. It counts what the app holds itself: point clouds (including the display copy), backups, octree tiles, the terrain model, the vertices of all shapes and their undo steps, plus under “other” the picking grid, the octree sorting and the render attributes. Not counted are GPU memory, textures, map tiles, labels, images and anything the browser itself holds. It is an estimate by the app, not the browser’s value (which does not count large data arrays). The number turns yellow from 4 GB and red from 8 GB; these are rules of thumb because the browser does not tell how much a tab really gets. The tooltip of the number shows the breakdown. If it is yellow or red: release backups, remove clouds you do not need or lower the octree tile memory.
Shapes as DXFThe app writes the shape DXF file in pieces; the only limit left is memory and whether your CAD program can still open the file. With a very large number of vertices (millions, e.g. after heavy densifying) still export in several parts (layer selection or boundary).

Work with your own point cloud.

Open point clouds, trace existing features and export geometry for CAD — directly in your browser, with point cloud data processed locally.

Try free for 14 daysRequest a demo