DWG vs PDF on iPad for site review: when the original drawing matters

If your iPad workflow is only about reading a sheet or sending a simple snapshot, a PDF is often enough. If the review still depends on the original drawing context, the DWG matters more. Keep the DWG when you need to switch layouts, isolate layers, verify a measurement, place a note on the right location, or export a handoff that still reflects the actual drawing instead of a flattened page.

That is the real decision behind DWG vs PDF site review. Search results often mix mobile CAD viewers, conversion tools, and PDF workarounds as if they solve the same job. They do not. A PDF is a convenient output. A DWG is still the working drawing when the review depends on context.

The short answer: when PDF is enough and when DWG matters

The distinction is practical, not ideological. Nobody needs the DWG all the time. But flattening too early creates avoidable site-review mistakes because the iPad loses the parts of the drawing that help you verify what you are looking at.

If the first blocker is simply getting the drawing onto the device, start with how to open DWG files on iPad without converting them. This article begins after the file is already in the workflow and you need to decide whether PDF is enough.

Why PDF feels easier, and where it starts failing

PDF wins on convenience. Everyone can open it, forward it, and archive it. That is why many teams flatten the drawing before they even know what kind of review they actually need.

That choice is fine when the drawing is only being:

• read as a reference
• printed or emailed as a static sheet
• shared with people who do not need any source-drawing context

The problem starts when the review is no longer passive.

On site, the useful questions are usually things like:

• "Are we on the right layout, or are we looking at the wrong sheet?"
• "Is this geometry missing, or is it just hidden inside a different layer state?"
• "Can I trust this dimension, or am I only measuring a flattened page?"
• "If I mark this issue here, will the next person understand the exact plan context?"

A PDF can still show the sheet. What it cannot do is preserve the deeper DWG review workflow around layouts, layers, and drawing-native context.

Apple's Files basics for iPad and file-open guidance for iPhone and iPad matter here because real review flows usually start in Files, Mail, AirDrop, or iCloud Drive. Once the drawing is local, the real question becomes whether you keep reviewing the DWG or collapse it into a PDF too early.

What the DWG preserves that a PDF cannot

Autodesk's current drawing file format compatibility reference is a good reminder that DWG files carry structured drawing information, and that version context still matters. Autodesk's broader viewer overview also validates that viewing, measuring, markup, and review belong to the CAD-file workflow, not only to exported outputs.

That matters on iPad because the original DWG preserves four things that often decide whether a site review is trustworthy.

1. Layout context

When a drawing looks empty, cropped, or wrong, the file is not always broken. Sometimes the wrong layout is active. That is why how to switch layouts and paper space on a DWG from iPad exists as a separate workflow. The right sheet context is often the difference between a useful field decision and a false alarm.

2. Layer control

Site reviews often fail because the drawing is too noisy, not because the file is unreadable. The official AutoCAD App Store listing and DWG FastView's official site both validate that mobile DWG viewing is expected to include layer-aware workflows. DWG FastView's own mobile layer guide makes that point explicitly.

If the job is to hide nonessential systems, isolate one discipline, or reduce visual clutter before measuring or annotating, the PDF version is already one step behind. The closer workflow is reviewing DWG layers on iPad during a site visit.

3. Measurement confidence

Some PDF workflows support basic measurement, but the stronger path is to verify the measurement from the drawing context you actually intend to trust. On iPad, that usually means confirming the right layout, the right layer state, and the right geometry before you measure.

If that is the task in front of you, how to measure distances on a DWG file from iPad is the better next step than exporting to PDF first.

4. Review-safe notes and handoff

A PDF can be a useful final deliverable. It is much weaker as the source of truth while the review is still happening. If you need to pin a note, clarify a site observation, or export the right current view after the review is complete, the DWG should stay in the workflow first and the PDF should usually come later.

A practical rule for site review: review in DWG, share in PDF

For many teams, the best answer is not choosing one forever. It is using each format at the right moment.

Use this sequence:

1. Open the original DWG on iPad from Files, Mail, AirDrop, or another local document source.
2. Confirm the right layout and visible layers before you trust what you see.
3. Verify the condition, note, or measurement that matters.
4. Finish the markup or observation in the drawing context.
5. Export a PDF, image, or report only when the review is ready to share.

That keeps the DWG where it adds value and keeps PDF where it is strongest: final distribution.

This is also why broad construction plan viewer pages can be misleading. What to look for in a construction plan viewer on iPad is really a category-decision article, while this piece is narrower: when the original drawing should remain live during the review itself.

When PDF is still the better choice

A fair comparison should say this plainly: PDF is often the better format when the review no longer depends on DWG-specific context.

Choose PDF first when:

• the recipient only needs a fixed sheet or snapshot
• the drawing has already been reviewed and approved in context
• the goal is broad distribution, not active drawing analysis
• the team needs a lightweight attachment for email, messaging, or downstream documentation

In other words, PDF is a strong output format. It is just a weaker working format when the review still depends on how the original drawing is structured.

The iPad workflow where DWG clearly wins

The original DWG matters most when the field reviewer still needs to think with the drawing, not just read it.

Common examples:

• a superintendent checking whether the team is discussing the correct sheet before a walkthrough
• an architect isolating one layer group to inspect a coordination issue
• an inspector confirming one dimension before capturing an observation
• a project lead adding a note in the exact plan location before exporting a handoff

That is the workflow described across the current PlanInspect cluster:

• A complete iPad DWG review workflow for construction teams for the full end-to-end sequence
• A DWG site walkthrough workflow for iPad teams for the field path
• How to export DWG markups and site notes as a PDF from iPad for the moment where PDF becomes the right output

What this looks like in PlanInspect

PlanInspect is strongest when the team still needs the original DWG on iPad, but does not need a full drafting workstation.

In that workflow, you can:

• open the DWG locally from Files, Mail, iCloud Drive, AirDrop, or the iOS share sheet
• keep model and layout context available during the review
• hide noisy layers before the drawing decision gets made
• measure distances and areas from the drawing you are actually reviewing
• attach notes and markups before the context disappears
• export the finished handoff as a PDF or report once the review is complete

That makes PlanInspect a strong fit when the team sounds like this:

• "We are still verifying the drawing, not just forwarding it."
• "We need the right layout before we trust the sheet."
• "We need to simplify layers before the condition is obvious."
• "We want to export a clean PDF after the review, not replace the review with a PDF from the start."

What to share after the review

The strongest handoff is often not "send the DWG to everyone." It is "finish the review in the DWG, then send the clearest output for the next person."

That output might be:

• a PDF of the reviewed sheet
• a focused image of the current view
• a notes report with the exact observation context

This is where PDF becomes useful again. It is often the right deliverable once the DWG review is complete.

Choose based on the job, not the file extension

For iPad site review, PDF is enough when the drawing is only being read, shared, or archived. The original DWG matters when the review still depends on layout, layers, measurement, markup, and drawing-native context.

That is the practical rule:

• Use PDF for lightweight reading and final sharing
• Keep the DWG for active review

If the team still needs to think with the drawing, do not flatten it too early.