DXF vs PDF vs OBJ vs XML: Which Floor Plan Export Format Do You Need?

Every export starts from the same scanned geometry, so it's tempting to treat the format as an afterthought — pick whatever you exported last time and move on. That habit is exactly how a structural engineer ends up with a PDF they can't measure off of, or a client gets a DXF file they have no idea how to open. The four formats aren't interchangeable wrappers around the same file; they're built for different jobs, and picking the wrong one costs someone else time, not you.

This is the reference we point people to when they ask "which format do I even send?" — what PDF, DXF, OBJ, and XML are each actually built to do, and how to choose based on who's opening the file rather than what you're used to exporting.

Why the Format You Pick Actually Matters

The underlying scan data is identical no matter which button you tap on the export screen — same walls, same dimensions, same room boundaries. What changes is how that data gets packaged for the next person in line. A PDF freezes the plan into a fixed, printable page. A DXF hands over live, editable vector geometry a CAD program can manipulate. An OBJ describes a 3D surface mesh for renderers. An XML lays the same data out as structured fields a piece of software can read without a human looking at it. Send the wrong one and the recipient either can't do their job with it, or has to ask you to redo the export — which, on a busy week, is a genuinely annoying way to lose twenty minutes.

PDF — For People, Not Programs

PDF is the format to reach for whenever a human is going to look at the plan and not do anything computational with it. It prints cleanly, opens on literally any device without special software, and — done right — includes a scale bar, dimension strings, and a room table so it's self-contained even without the original project file behind it.

That's exactly why it's the default for client deliverables, listing documents, and most building department counters: see our guides on floor plans for real estate listings and as-built plans for permit applications for the specifics of preparing a PDF for each. The tradeoff is that a PDF is a picture of the geometry, not the geometry itself — nobody can select a wall in a PDF and see its length update live, and a plan reviewer or engineer working in CAD can't build on top of it directly.

DXF — For CAD and Any Trade That Draws

DXF is a vector CAD format — it carries real geometry, organized into layers, that opens directly in AutoCAD, Revit, and nearly every drafting tool in professional use. Walls, doors, windows, room labels, and dimension annotations each live on their own layer, so a recipient can toggle what they need, snap to your walls when drawing on top of them, and trust the dimensions are live values rather than printed text.

Send DXF to anyone who's going to draw on top of your plan rather than just look at it: an architect or engineer building proposed drawings on your existing conditions, an electrician or HVAC contractor laying out a system, or a structural reviewer checking load paths. For multi-story buildings, each level exports to its own set of layers so the file stays organized floor by floor — our multi-level commercial guide covers how that structure holds together across a whole building. And because DXF follows the same drafting conventions — wall weights, door swing arcs, dimension notation — as hand-drafted plans, our floor plan symbols and abbreviations reference is worth having open the first few times you're reading one back.

OBJ — For 3D Visualization and Rendering

OBJ is the odd one out on this list, and most professional workflows on this blog never touch it — it's a 3D mesh format, not a 2D drafting one. It describes the scanned space as a surface model: walls with height and thickness, floors, and ceilings as actual 3D geometry, importable into Blender, SketchUp, Unity, or any renderer that reads OBJ. That makes it the right choice when the deliverable is a visual — a walkthrough render, a marketing visualization, a VR mockup — rather than a measured document someone will build from or submit officially.

Don't reach for OBJ when what you actually need is precise 2D dimensions or CAD-editable geometry; a 3D mesh isn't built for that kind of measurement work, and DXF will serve you far better there.

XML — For Structured Data and Software Integrations

XML packages the same room, wall, door, window, and dimension data as structured fields rather than a drawing — meant to be read by another piece of software, not by a person opening a file. Nobody prints an XML export or hands it to a client; it exists to feed a downstream system without anyone re-typing dimensions by hand.

The clearest example is property-loss estimating: adjusters export XML because it maps cleanly into the room-sketch concepts mainstream estimating platforms use, turning a scan directly into estimate line items instead of a manual re-measurement. Our insurance adjuster workflow guide covers that integration in detail, and the schema follows the same room-by-room logic behind the repair cost estimate export. If you're building a custom pipeline and want the field mapping, that's exactly the kind of documentation support@vplan.ai can walk you through.

Choosing by Recipient, Not by Habit

The fastest way to pick correctly is to ask one question before you export: what is this person going to do with the file? A buyer or client reading a plan on their phone wants PDF. An architect, engineer, or trade drawing on top of your existing conditions wants DXF. Estimating or claims software wants XML. A 3D artist or marketing team building a render wants OBJ. A building department could go either way — check their submission checklist, since some accept a dimensioned PDF and others specifically want DXF for anything beyond the simplest scope.

When you genuinely don't know, PDF is the safer default — everyone can open it, even if it's not the most useful format for their downstream work — but it's worth asking rather than guessing whenever the stakes are higher than a quick look.

One Scan, Every Format — No Redrawing Required

None of this requires committing to one format per project. Every scan in vPlan AR can be exported to PDF, DXF, OBJ, and XML independently, as many times as you need, because they're all generated from the same captured geometry rather than redrawn from scratch. Scan once, and send the engineer a DXF, the client a PDF, and the estimating platform an XML — all from the same site visit.

If you need to add a scale bar, north arrow, or extra annotations before an export goes out, the web editor is the easiest place to do that polishing on a larger screen before generating the final file.

Frequently Asked Questions

What's the difference between DXF and PDF for a floor plan?

A PDF is a fixed, print-ready page with no live geometry — good for a person to read, not for a program to edit. A DXF is a vector CAD file with real, editable geometry organized into layers, meant for a program like AutoCAD or Revit to open and build on.

Can I open an OBJ floor plan file in AutoCAD?

Not usefully as a floor plan. OBJ is a 3D mesh format meant for renderers and 3D viewers like Blender, SketchUp, or game engines, not 2D CAD drafting — use DXF instead for anything that needs precise, editable 2D geometry.

What export format do insurance adjusters use for floor plans?

Most adjusters export XML for structured room and dimension data that maps into their estimating software, alongside a PDF kept in the claim file for documentation.

Do I need to rescan a space to get a different export format?

No. Once a space is scanned, the same project can be exported to PDF, DXF, OBJ, or XML at any time, since every format is generated from the same captured geometry rather than redrawn.

Which format do building departments want for a permit floor plan?

It depends on the jurisdiction and project scope. Most residential submissions accept a dimensioned PDF, but anything headed to an architect or engineer for CAD work, or larger and more complex jurisdictions, often specifically wants DXF.