DWG and DXF takeoff in the browser, not just PDF

Almost every takeoff tool starts from a PDF, and a PDF is a picture. The scale has to be set by hand, the lines are pixels, and the levels are whatever the drafter printed as text. When the surveyor or civil engineer sends the actual drawing file, that file has real coordinates, named layers and, often, the existing surface itself.

SitesAI Estimate opens DWG and DXF directly, in the browser, alongside PDF. That is the difference between tracing a picture and measuring a drawing.

Which files open, and how?

Large files are streamed as a compact scene rather than loaded whole, so a survey with tens of thousands of entities still opens on a normal laptop. This was hardened against forty real drawings from a working earthmoving contractor before release — the kind with stray geometry a long way from the site, mixed units and blocks inside blocks.

Layers you can see

A CAD drawing is organised in layers: boundary, existing contours, design contours, services, text. SitesAI Estimate lists the layers on the page, so you can hide the noise and measure from the one that matters. When you trace a platform from the DESIGN layer, you are snapping to the engineer's line, not to a printed approximation of it.

Units and scale

A DXF declares its units in the file header. When it does, the layer is calibrated the moment it opens: no scale bar, no known dimension, no guessing. When a file does not declare units — it happens more often than it should — the app makes a sensible guess from the geometry and marks the layer uncalibrated until you confirm it. That flag is deliberate. A drawing in millimetres read as metres is a thousand-fold error, and the app would rather ask than assume.

Levels straight from the survey

This is where CAD files earn their keep. Contours and spot levels in a survey DXF carry elevation values. SitesAI Estimate can import them into the existing ground surface as an opt-in step: open the layer editor, choose the contour and spot-level layers, and the terrain is built from the surveyor's data rather than from levels you typed off a PDF.

From there the workflow is the same as any job: set the design levels for the platform, roads or batters, and read the cut and fill. Open the 3D view to check the shape looks like the site you walked.

When is a PDF still fine?

Not every job comes with CAD. A site plan from an architect, a council approval set or a builder's sketch is a PDF, and SitesAI Estimate handles that with scale calibration and manual levels. Many jobs are a mix: a PDF plan for the footprint and a DXF survey for the ground. Because layers are independent, you can align the two to shared points and measure across both.

What to watch

• Civil 3D objects. Surfaces and corridors saved as proprietary objects come through as their exploded geometry or their proxy graphics. The contours and points you need are almost always present as plain entities; a true 3D surface object is not.
• Wrong units in the file. The uncalibrated flag catches missing units, not wrong ones. If a drafter drew in feet and declared metres, only you will notice — check one known dimension.
• Enormous exports. A full-corridor design export can be hundreds of megabytes. Ask for the sheet you need, or the layers you need, rather than the whole model.

The point of all this is simple: measure from the file the engineer actually sent, with the levels already in it, and get to a cut-and-fill number the same afternoon. Sign in to SitesAI Estimate, add a layer, and choose the DWG or DXF.