What to check when a DWG file will not open on iPad

When a DWG file will not open on iPad, the cause is usually simpler than people expect: the file is not a real DWG, the transfer was incomplete, the file is opening through the wrong Files flow, or the drawing uses a DWG version or data the viewer cannot render cleanly yet. Start with the file itself, resend it once, open it again from Files, and only then treat it as a deeper compatibility problem.

That sequence is much faster than converting the drawing to PDF and losing the DWG context you were trying to review in the first place.

Quick checklist when a DWG will not open on iPad

Use this order before you blame the device or switch workflows:

If you are still comparing mobile viewers at the category level, how to choose a DWG viewer for iPad is the broader buying guide. This article is the narrower "why did this real file fail today?" version.

1. Confirm it is a real DWG file

This sounds obvious, but it is the fastest check and it resolves more failures than most teams admit.

PlanInspect's own support guidance already points to the first question: is the file really a valid .dwg, or is it a renamed .dxf, .pdf, or other attachment? If the extension looks right but the file came from a messy email thread, a shared-folder export, or a manual rename, treat the source file as suspicious first.

That matches the product behavior in practice. A non-DWG file never gets to the drawing stage cleanly because the app validates that it is opening a .dwg before rendering starts.

If your team needs the clean import path itself, how to open DWG files on iPad without converting them walks through the local workflow from Files and the share sheet.

2. Re-send or re-download the file once before going deeper

If a DWG will not open, do one boring thing before you do any clever troubleshooting: send the file to the device again.

That advice is already consistent with PlanInspect's support copy: partial downloads or corrupted transfers are often the most common cause. It is especially plausible when the file arrived through:

• AirDrop during a rushed handoff
• an email attachment that did not finish downloading
• a cloud folder that cached partially
• a message thread where the wrong revision was saved locally

Apple's Files guide for finding and viewing files on iPad is useful here because it reflects the real iPad workflow: search the file, confirm its location, and deliberately reopen the version you actually intend to use.

The key point is not "use AirDrop" or "use cloud storage." The key point is to refresh the local copy once before assuming the drawing is permanently broken.

3. Open it from Files and choose the correct app path

Sometimes the issue is not the DWG itself. The issue is how iPad is trying to open it.

Apple's current Files documentation makes two relevant points:

• Files is the main place to locate and reopen the document you want.
• You can choose or change which app opens a file from the file info flow.

That matters because a drawing can appear to "not open" when iPad is trying to preview it, route it through an unexpected app, or reopen an older default behavior. If tapping the file does not get you to the viewer you expect, try:

1. finding the file again in Files rather than only reopening it from Recents
2. touching and holding the file to inspect its info
3. reopening it with the intended viewer instead of whatever the system chose first

If your team also checks drawings on phones during handoff, the DWG viewer on iPhone guide explains the same local-first principle on the smaller screen.

4. Check DWG version and file complexity

If the file is real and the transfer is clean, the next question is compatibility.

Autodesk's DWG drawing file format compatibility reference is the right reminder here: DWG files vary by version, object mix, and overall complexity. In other words, "it is a DWG" is not the same as "every viewer will render it the same way."

This is also where the app's actual parser behavior matters. PlanInspect surfaces explicit unsupported-version errors instead of silently pretending the drawing is fine. The parser also throws clear failures for invalid signatures, file sizes that are too small, and damaged compressed sections.

That gives you a more useful diagnosis path:

• if one known-good project DWG opens but this one does not, compare the source and version history
• if archive drawings fail while current drawings open, suspect an older or unusual format variant
• if the file is extremely dense, heavy with hatches, blocks, or complex geometry, test whether the problem is complexity rather than the iPad itself

The right field habit is to test one messy production drawing before you standardize a workflow, not just a clean vendor sample.

5. If the drawing opens but looks wrong, check layout, layers, and units

Searchers often say "the DWG won't open" when the drawing technically opened but the result looks unusable.

That can mean:

• the wrong layout is active
• the layers that matter are hidden or turned off
• the element you expect is on a different sheet context
• a measurement looks wrong because the source units are wrong

Those are not import failures. They are drawing-context failures.

If parts of the plan seem to be missing, start with reviewing DWG layers on iPad. Hidden or noisy layers are a much more common explanation than a mysterious rendering failure.

If the file opens but the wrong sheet seems to be active, how to switch layouts and paper space on a DWG from iPad is the direct follow-up. Layout confusion is one of the fastest ways to mistake a usable drawing for a broken one.

If the file opens but the dimensions seem off, use the checks in how to measure distances on a DWG file from iPad. A bad unit setup in the source drawing can make a clean-looking measurement unreliable.

This distinction matters because the fix is different. If the problem is context, converting the drawing to PDF will not solve the underlying confusion. It will usually make later review harder.

When to stop troubleshooting and contact support

Once you have checked the file type, resent the file, reopened it from Files, and ruled out obvious layout or layer confusion, stop improvising and send a useful support report.

The support page is the right internal handoff point. Include:

• the exact file name
• where the file came from: Files, AirDrop, Mail, cloud storage, or another source
• whether other DWGs open on the same device
• whether this file fails completely or opens with missing content
• the DWG version or source application if you know it

That gives support a real chance to separate a damaged file from an unsupported version or a renderer gap.

What this looks like in PlanInspect

PlanInspect is strongest when the goal is to keep the original DWG usable on iPad, not to force a detour through conversion.

That workflow is straightforward:

• open the local file from Files, Mail, AirDrop, iCloud Drive, or the share sheet
• surface an explicit unsupported-file or unsupported-version state when the file is not ready for review
• move into layout, layer, measurement, note, and export workflows once the drawing opens cleanly

That makes PlanInspect a good fit when your real troubleshooting question is not "How do I flatten this into something else?" but "How do I get the actual DWG back into a usable field workflow?"

Fix the cause, not just the symptom

When a DWG file will not open on iPad, the fastest fix is usually not another conversion step. It is a better diagnosis order.

Check whether the file is a real DWG, resend it once, reopen it from Files, confirm version compatibility, and only then treat it as a deeper rendering problem. If the drawing opens but feels wrong, switch your diagnosis from import to layout, layers, and units. That is the difference between a one-off workaround and a field workflow you can trust again tomorrow.