Intro

You’ve done the design work. The model looks right, the dimensions check out, everything looks clean inside your CAD software. Then you export the file, send it downstream, and something breaks.

Maybe the geometry comes out wrong. Maybe the vendor can’t open it. Maybe the bend lines are missing, the metadata is gone, or the file opens fine but the dimensions are off by some factor that doesn’t make sense until you realize it’s a unit conversion issue.

CAD file format problems are one of those frustrations that never fully disappear — not because engineers aren’t careful, but because the ecosystem of formats, software versions, and downstream requirements is genuinely messy. Different tools, different standards, different expectations. And the cost of getting it wrong ranges from a minor annoyance to a scrapped production run.

Here are the seven most common CAD file format problems engineers run into, what actually causes them, and what you can do to fix or prevent them.

1. Broken or Missing Geometry After Export

This is the one that causes the most panic. You export a DXF or STEP file, the recipient opens it, and geometry is missing — arcs are gone, curves have turned into jagged lines, or entire features have disappeared.

What causes it:

Most CAD formats don’t store geometry the same way your native software does. When you export, the software has to translate its internal representation into the target format’s structure. If that translation doesn’t handle splines, complex curves, or surface types correctly, you lose fidelity.

The root cause goes deeper than export settings — it’s the geometric kernel. SolidWorks uses Parasolid, Inventor uses ShapeManager (an ACIS fork), and FreeCAD uses OpenCASCADE. Each kernel represents surfaces, trimming curves, and edge tolerances differently. When a Parasolid surface gets translated to STEP entities through sldstepu.dll, or an ACIS surface goes through Inventor’s ATF framework (atf_step_producer.dll), the translation makes representation choices that can lose fidelity on complex curved geometry. A fillet that’s a clean analytic torus internally may become a NURBS B-spline surface in the STEP file — and the receiving system may not recognize it as a fillet at all. (Our STEP format deep dive explains exactly how each kernel’s translator works.)

It also happens when export settings aren’t configured properly. Exporting a 3D body as a 2D DXF without flattening it correctly, for example, can produce empty or corrupted output.

How to fix it:

  • Always open and visually inspect exported files before sending them
  • Match the export format to what the downstream tool actually needs — STEP handles 3D solids better than IGES in most cases. See our DWG vs DXF vs STEP vs IGES comparison for a detailed breakdown of format strengths.
  • For DXF exports, confirm you’re exporting from the correct plane or face, not the full 3D model
  • Check your spline and curve export settings — some formats require converting splines to polylines or arcs

If you’re doing this repeatedly across many parts, manual inspection doesn’t scale. Automating exports with consistent, pre-validated settings removes most of the human error that causes this in the first place.

2. Wrong Units After Import

A part that’s 100mm long opens in the recipient’s software as 3.937 inches — or worse, as 100 inches. Unit mismatches are surprisingly common and surprisingly destructive when they go unnoticed.

What causes it:

Some CAD formats embed unit information in the file header. Others don’t. When the receiving software doesn’t find explicit unit data, it defaults to its own settings, which may not match what the sender intended. DXF files are a frequent offender here. The format supports unit declarations, but not all software writes them correctly, and not all software reads them.

How to fix it:

  • Always declare units explicitly in your export settings — don’t rely on software defaults
  • Include unit information in your file naming convention or accompanying documentation
  • When receiving files, confirm units before doing anything else — most CAD tools let you check and rescale on import
  • Establish a team-wide standard for export units and stick to it

This is almost entirely preventable with consistent process. The issue isn’t the format — it’s the lack of standardization around how files get exported.

3. Missing Bend Lines and Sheet Metal Data in DXF Exports

This one is specific to sheet metal work, but it’s extremely common and genuinely costly. You export a flat pattern as DXF for a fabricator, and the bend lines aren’t there. Or they’re on the wrong layer. Or the bend direction information is lost entirely.

What causes it:

Sheet metal DXF exports require specific configuration to include bend line geometry and associated metadata. In SolidWorks, for example, the default DXF export doesn’t always include bend lines unless you’ve explicitly set up the export to output them on the correct layers. Fabricators often have specific layer naming requirements — if your bend lines are on a layer called “BEND” but they expect “BEND-UP” and “BEND-DOWN,” they can’t use the file without manual rework.

How to fix it:

  • Configure your DXF export template to include bend lines on the correct layers before anything goes to fabrication
  • Confirm layer naming conventions with your fabricator upfront — get their template requirements in writing
  • Include bend angle and direction metadata in the export, not just the geometry
  • Test your export settings on a known part before rolling them out to a full batch

This is exactly the kind of problem CadShift is built to solve. Its SolidWorks plugin handles batch DXF export with bend lines and metadata baked into the workflow — so you’re not reconfiguring settings every time or hoping the manual export captured everything correctly. For a detailed walkthrough of proper sheet metal DXF export, see our batch DXF export guide for SolidWorks.

4. Version Incompatibility Between CAD Software

You save a file in the latest version of your software. The vendor opens it in a version from three years ago. It either won’t open at all, or it opens with missing features, degraded geometry, and a warning that something was lost in translation.

What causes it:

CAD formats evolve. Native formats like .sldprt or .dwg are version-specific — a file saved in SolidWorks 2024 may not open cleanly in SolidWorks 2021. Even neutral formats like STEP have revision levels (AP203, AP214, AP242) that not all software versions support equally.

How to fix it:

  • When sharing files externally, use neutral formats (STEP, IGES, DXF) rather than native formats unless you know the recipient is on the same software version. Understanding how to convert CAD files between formats helps you choose the right neutral format for each situation.
  • If you must share native files, save down to the lowest version the recipient is running
  • For DWG files, explicitly set the save version — AutoCAD lets you save back to R14 if needed
  • Document your software version in project metadata so recipients know what they’re working with

The longer-term fix is to standardize on neutral exchange formats for anything leaving your organization. Native formats are for internal use.

5. Translation Errors in Complex Assemblies

Single parts usually translate cleanly. Assemblies are a different story. References break, components go missing, or the assembly opens with parts in the wrong position. Sometimes everything looks fine until you try to interact with it and realize nothing is properly constrained.

What causes it:

Assembly files depend on references — to part files, sub-assemblies, external sketches. When you export or move an assembly, those references can break if file paths change or if the export format doesn’t preserve the relational structure. STEP handles assemblies reasonably well, but even STEP exports can lose constraint information, leaving parts floating in space.

How to fix it:

  • Use “pack and go” or equivalent tools to bundle all referenced files before sharing
  • For STEP exports of assemblies, verify that all components are included and positioned correctly in the exported file
  • Flatten complex assemblies into a single solid body when the recipient only needs the geometry, not the structure
  • Keep assembly folder structures consistent and don’t move files after references are established

If you’re regularly exporting assemblies for downstream use, building a checklist into your export process prevents the most common reference-breaking mistakes.

6. Lost or Stripped Metadata

The geometry is fine. The file opens correctly. But the part number is gone, the material specification isn’t there, the revision level is missing. Whoever receives the file has to follow up for information that should have been in the file to begin with.

What causes it:

Many export formats don’t support the same metadata fields that native CAD formats do. When you export from SolidWorks to DXF, custom properties like part number, description, material, and revision don’t automatically carry over unless you’ve configured the export to include them. In some formats, metadata can be embedded in the file header or in attributes — but only if your export settings are set up to write it.

How to fix it:

  • Define which metadata fields are required in every exported file and configure your export templates accordingly
  • Use format-appropriate metadata containers — DXF supports block attributes, STEP supports product data fields
  • Validate that metadata is present in exported files before they leave your system
  • For high-volume exports, automate metadata population from a master source rather than relying on manual entry

This is another area where automation pays off quickly. When you’re exporting dozens or hundreds of parts, manually verifying metadata on each file isn’t realistic. CadShift’s batch export workflow handles metadata inclusion as part of the process, keeping it consistent across every file in the batch.

7. Inconsistent Outputs Across Repeated Exports

You export the same part twice and get slightly different results. Layer assignments shift. A line that was in one place is now somewhere else. A dimension that exported correctly the first time is missing the second. The geometry is technically the same, but the file isn’t.

What causes it:

This happens when exports are done manually with settings that aren’t locked down. If different engineers are exporting files using their own local settings — or if settings drift as software updates change defaults — you get inconsistent outputs. It’s also common when exports are done in a hurry and settings aren’t double-checked.

How to fix it:

  • Create and enforce shared export templates that all engineers use — don’t let settings live on individual machines
  • Lock down export configurations so they can’t be accidentally changed
  • Run exports through a defined, repeatable process rather than ad hoc
  • Periodically audit exported files against your standards to catch drift early

The root cause here is process, not software. Manual, person-dependent workflows produce inconsistent results by definition. The fix is to remove the variability — which means either extremely strict documentation and enforcement, or automation that eliminates the manual steps entirely.

The Pattern Underneath All of These Problems

Look at these seven problems together and two patterns emerge.

The first is process. Units get lost because nobody standardized the export settings. Metadata goes missing because the export template wasn’t set up to include it. Bend lines disappear because the manual export process didn’t account for fabricator requirements. Outputs are inconsistent because different people are doing the same task differently. The fix for a process problem isn’t to be more careful — it’s to make the correct behavior the default.

The second pattern is deeper: different CAD systems use different geometric kernels, and those kernels make different decisions about how to represent, translate, and export geometry. A fillet created by Parasolid’s PK_EDGE_set_blend_constant in SolidWorks is a fundamentally different surface than the same fillet created by OpenCASCADE’s BRepFilletAPI_MakeFillet in FreeCAD — different NURBS representations, different trimming curves, different tolerance regimes. When these surfaces get written to STEP files, they carry the fingerprints of the kernel that created them. This is why the same part modeled in two different CAD systems can produce STEP files that look the same but behave differently during import, FEA meshing, or CNC toolpath generation. Our kernel fillet comparison shows exactly how these differences manifest at the DLL level.

If your team is experiencing these problems regularly, it may be one of the signs you need CAD automation software.

Conclusion

CAD file format problems are frustrating precisely because they’re so preventable. The geometry was right. The design was solid. The file just didn’t survive the translation.

The engineers who deal with these problems least often aren’t necessarily more careful — they’ve built workflows that handle configuration, consistency, and validation automatically. Shared templates. Locked settings. Batch processes that produce the same output every time, regardless of who runs them.

If you’re running into these issues regularly — especially around DXF exports with sheet metal data or batch conversion workflows — it’s worth asking whether your current process is set up to prevent them or just respond to them.

Learn more at Cadshift.com.