How to Convert SolidWorks Files to STEP Format: The Complete Guide

How to Convert SolidWorks to STEP — The Quick Answer and Why It’s Rarely Enough

To convert SolidWorks to STEP format, open the part or assembly, go to File > Save As, choose STEP AP214 (or AP203/AP242) from the type dropdown, click Options to set version and geometry flags, then hit Save. This takes about thirty seconds for a single file. Got one file and some spare time? You’re done.

But most engineers don’t work with single files. They’re dealing with fifty parts. Or five hundred. They have assemblies packed with nested components, revision cycles that demand re-exporting the same geometry every time something changes, and downstream teams — machinists, simulation analysts, procurement — who need consistent, clean STEP files without waiting for someone to manually click through dialogs.

This guide covers everything: what STEP actually is, how to export it from SolidWorks properly, what goes wrong during conversion and why, plus how to stop doing it by hand when volume or repeatability becomes your real challenge.

What STEP is and why it matters

STEP stands for Standard for the Exchange of Product model data. It’s an ISO standard (ISO 10303) built specifically to transfer 3D geometry, product structure, and associated data between different CAD systems without losing fidelity.

Unlike proprietary formats like .SLDPRT or .SLDASM, STEP files are neutral. A manufacturer running CATIA, a supplier using Fusion 360, and a simulation engineer on Ansys can all open the same .stp file without needing a SolidWorks license. If you’re weighing which CAD platform fits your team best, our SolidWorks vs Fusion 360 vs Inventor comparison covers the key trade-offs. If that decision includes cloud vs. desktop hosting, our cloud CAD vs desktop CAD comparison covers data sovereignty and offline access considerations that affect how STEP files flow between teams.

That neutrality is the whole point. STEP is the lingua franca of mechanical engineering data exchange. For a deeper look at what STEP actually contains — how each kernel serializes geometry, what AP203/AP214/AP242 encode differently, and why a STEP file from SolidWorks isn’t identical to one from Inventor for the same nominal model — see the STEP file format explained. For a broader look at how STEP fits alongside other neutral formats like DXF and IGES, see our guide to converting CAD files between formats.

STEP AP203 vs AP214 vs AP242 — Which Version to Choose When Exporting from SolidWorks

SolidWorks offers three STEP Application Protocol variants. The difference matters based on what data needs to survive the transfer. A dedicated deep-dive on the version differences is at our STEP AP203 vs AP214 vs AP242 comparison.

AP203 — Configuration Controlled Design (1994)

AP203 covers 3D B-Rep geometry, topology, and basic product structure (assemblies). It does not carry colors, layers, surface finish annotations, or GD&T.

Use AP203 when:

• You don’t know what STEP version the recipient’s system supports
• You’re sending to an older CAM system (Mastercam v8-era, older ACIS-based importers)
• Pure geometry is all that matters — no visual organization, no annotations
• The recipient explicitly asks for “plain STEP” without specifying a version

Avoid AP203 when:

• Your model has a color-coded assembly (the colors won’t transfer)
• You need GD&T or PMI to arrive at the other end

AP214 — Core Data for Automotive Mechanical Design (1998, revised 2010)

AP214 is a superset of AP203 that adds colors, layers, some product structure attributes, drawing revision data, and surface finish codes. It’s the most widely deployed STEP version in the manufacturing supply chain.

Use AP214 when:

• Your assembly uses component colors for visual organization (BOM color coding, clearance zone visualization)
• You’re sending to a machining or fabrication supplier and want the geometry organized in a familiar layer structure
• The recipient uses a mainstream CAM system (Mastercam, HSMWorks, EdgeCAM, PowerMill) — all support AP214
• You’re unsure between AP203 and AP214: AP214 is backward-compatible and any system that reads AP203 reads AP214 cleanly

AP242 — Managed Model-Based 3D Engineering (2014, Amendment 1: 2020)

AP242 is the current standard. It merges AP203 and AP214 into a single unified schema and adds:

• Full PMI (Product and Manufacturing Information) — GD&T annotations, datum references, tolerances
• 3D annotations embedded in the model geometry (Model-Based Definition)
• Kinematics and motion constraints
• Validation properties for checking round-trip fidelity
• Composite material definitions

Use AP242 when:

• Your model has GD&T/tolerancing that the recipient needs (not just for reference — for actual CNC setup)
• You’re following a Model-Based Definition workflow where drawings are replaced by annotated 3D models
• Your customer or contract specifies AP242
• You’re sending to a simulation or FEA system that can consume PMI for automatic boundary condition setup

What SolidWorks actually exports for each variant:

SolidWorks’ STEP translator is sldstepu.dll, which calls Parasolid’s PK_PART_transmit to serialize geometry, then passes the result to catssdstepform.dll (Dassault’s ISO 10303-21 writer) for file formatting. The AP version selection changes what entity types get written:

SolidWorks AP242 gotcha: SolidWorks exports AP242 geometry cleanly, but PMI export requires that your model annotations were created as 3D annotations (DimXpert or MBD annotations), not drawn on a 2D drawing. If your GD&T lives in a 2D drawing only, AP242 export produces the same geometry as AP214 — the annotations stay in the drawing file.

For Inventor users: Inventor’s STEP export (via the ATF translator, not Parasolid/CATIA) supports AP203, AP214, and AP242 through Inventor 2024+. Older versions (pre-2022) don’t support AP242 and default to AP214. The color transfer fidelity from Inventor to STEP AP214 is generally better than SolidWorks because Inventor’s DWG kernel tracks display colors as explicit attributes rather than visual overrides.

For most fabrication handoffs, AP214 is the safe default. Use AP242 only when your downstream system specifically supports and needs the PMI data.

How to convert SolidWorks files to STEP manually

Here’s the standard export process in SolidWorks. Works for both parts (.SLDPRT) and assemblies (.SLDASM).

Exporting a single part or assembly

1. Open the file in SolidWorks.
2. Go to File > Save As.
3. In the “Save as type” dropdown, select STEP AP214 (or AP203/AP242 depending on your requirements).
4. Choose your output directory.
5. Before clicking Save, click Options — this is where most engineers skip a step they shouldn’t.

Configuring STEP export options

The Options dialog controls what actually ends up in your STEP file. These settings map directly to user preferences in the SolidWorks API — swStepAP (value 75) for AP version, swStepExportSplitPeriodic (396), swStepExportFaceEdgeProps (397), swStepExport3DCurveFeatures (497), and swStepExportConfigurationData (403). Key settings to review:

• Export 3D curve data (swStepExport3DCurveFeatures) — Include this if your downstream tool needs curve geometry, not just surfaces and solids.
• Export sketch entities — Usually off for fabrication handoffs; leave it on if you’re passing the file to another CAD environment that needs construction geometry.
• Split periodic faces (swStepExportSplitPeriodic) — Splits cylindrical and toroidal faces at seam lines. Some receiving systems (particularly older ACIS-based tools) can’t handle periodic surfaces. If your recipient uses Inventor or an ACIS-based CAM system and reports import errors on cylindrical holes, try enabling this.
• Save tessellation with BREP data — Useful if the recipient might render the file without a full STEP kernel.

Set your options, click OK, then Save.

What happens under the hood

When you click Save, SolidWorks doesn’t just “write” a STEP file — it runs a translation pipeline through three DLLs. First, Parasolid (pskernel.dll) serializes the B-Rep geometry via its PK_PART_transmit functions. Then sldstepu.dll (SolidWorks’ dedicated STEP translator) converts that Parasolid geometry into STEP entities through its RunSldStepDLL entry point. Finally, catssdstepform.dll — a Dassault Systèmes component inherited from CATIA — handles the ISO 10303-21 file format serialization. This CATIA heritage means SolidWorks’ STEP output has characteristics influenced by Dassault’s data exchange philosophy, not Parasolid’s. For the full technical breakdown of how this compares to Inventor’s ATF-based and FreeCAD’s OCCT-based STEP translators, see our STEP format deep dive.

Checking your output

Don’t assume the export worked just because no error dialog appeared. Open the STEP file in a neutral viewer — eDrawings, FreeCAD, or an online viewer like 3D Viewer Online — and verify:

• All bodies are present
• No geometry is missing or malformed
• Assembly structure is intact (for .SLDASM exports)
• Colors and layers transferred if you needed them

SolidWorks will occasionally export a STEP file that opens without error but is missing suppressed components, has broken references, or has geometry that downstream tools flag as invalid. Spot-checking saves headaches later.

Common problems during SolidWorks to STEP conversion

Missing or broken geometry

This usually happens with complex surfaces, imported geometry, or bodies that have errors in the SolidWorks model itself. Run Tools > Evaluate > Check on your part before exporting to catch geometry issues at the source.

Fillets and blends are particularly vulnerable. Parasolid creates blend surfaces using its rolling-ball algorithm (PK_EDGE_set_blend_constant), and these surfaces may be clean analytic tori internally. But when they intersect with other features, Parasolid’s boolean engine trims them, often converting clean analytic surfaces into NURBS approximations. The STEP translator writes whatever representation Parasolid gives it — so a fillet that looks perfect in SolidWorks may arrive as a NURBS surface that the receiving system’s feature recognition doesn’t recognize as a fillet. Our kernel fillet comparison explains why this happens at the DLL level.

If you’re working with a STEP file you received rather than one you’re exporting — and SolidWorks refuses to open it with “Failed to create empty document” — see the corrupt STEP assembly recovery guide for a workflow that extracts usable geometry using OnShape’s permissive validator and FreeCAD’s OpenCASCADE repair tools.

Assembly components not included

If you export a top-level assembly and some components are missing in the STEP output, check whether those components are suppressed or lightweight. SolidWorks won’t export suppressed components, and lightweight components may not fully resolve before export. Resolve all components to full detail before running the export.

Loss of PMI and annotations

AP203 doesn’t carry annotations. If you’re using GD&T in your model and need it to transfer, you must export as AP242. Sending AP203 to a recipient expecting PMI data means they get geometry only — all the tolerancing information stays behind.

File naming and metadata inconsistency

When you’re exporting manually, it’s easy to end up with inconsistent file names, missing revision indicators, or STEP files that don’t match the part number scheme your team uses. Minor annoyance with one file, serious problem at scale. Establishing solid CAD file management practices helps prevent this from spiraling.

STEP Conversion Errors — Exact Error Messages and Fixes

SolidWorks’ STEP translator fails in specific, recognizable ways. These are the exact messages with their causes and fixes.

“Unable to save the document to the file”

This export-side error has three common causes.

Path too long. Windows enforces a 260-character path limit (MAX_PATH). Deeply nested output folders with long project names and long part numbers hit this silently — the error message doesn’t mention path length. Fix: export to C:\temp\ and move the file afterward. If you’re running Windows 10 version 1607+ with long path support enabled in Group Policy (Computer Configuration > Administrative Templates > System > Filesystem > Enable Win32 long paths), the limit is lifted, but SolidWorks itself needs to be restarted after the policy change.

Output file locked. If you previously exported a STEP file and it’s open in a viewer, SolidWorks can’t overwrite it. Close all STEP viewers before re-exporting.

Write permissions. Network drives with restrictive ACLs will block the export. Export to a local path first, then copy to the network share.

“1 entity(ies) not imported” (in import diagnostics)

This warning appears in the Import Diagnostics feature tree item after opening a STEP file. It means at least one entity in the file wasn’t translated into SolidWorks geometry.

If the model looks visually complete, the unimported entity is almost always a decoration — a layer assignment, coordinate system, annotation, or surface orientation marker — rather than load-bearing geometry. Expand the Import Diagnostics item in the feature tree to see the entity type. If it reads GEOMETRIC_REPRESENTATION_ITEM, that’s real missing geometry. If it reads something like STYLED_ITEM or PRESENTATION_LAYER_ASSIGNMENT, the geometry itself is intact.

For actual missing geometry: open the STEP file in FreeCAD. FreeCAD’s OpenCASCADE importer accepts entity types that SolidWorks’ Parasolid-based translator drops. From FreeCAD, re-export as STEP AP214 — this reformats the problem entity into a cleaner representation that SolidWorks accepts on the second pass.

“Cannot import this file. The file is not valid” or “Problem reading this document”

Three causes:

1. Corrupted file transfer. STEP files are 7-bit ASCII text. If a file was transferred via FTP in binary mode, or passed through a broken zip utility that converted line endings, the file structure breaks. Open the STEP file in Notepad or VS Code. Line 1 must be exactly ISO-10303-21; (with a semicolon, no spaces). Each DATA section line must end with a semicolon. If the file looks like binary garbage or has garbled line endings, the transfer was the problem.

2. AP242 opened in SolidWorks 2021 or earlier. AP242 support was added in SolidWorks 2022. Opening an AP242 STEP file in an older version produces this error. Inspect line 5 of the STEP file header — it reads FILE_SCHEMA(('AP242_MANAGED_MODEL_BASED_3D_ENGINEERING_MIM_LF { 1 0 10303 442 1 1 4 }')) for AP242. If so, upgrade SolidWorks or ask the sender to re-export as AP214.

3. Non-standard STEP dialect. Some CATIA V5 exports include Dassault-internal entity extensions not recognized by SolidWorks’ translator. Pass the file through FreeCAD (which strips unrecognized extensions) and re-export as standard AP214.

Zero bodies imported / “No solids were translated”

The STEP translation completed but SolidWorks has no geometry to show.

• Wire-only geometry. STEP can carry edges without faces — a wire frame model. SolidWorks only imports solid bodies. Open in FreeCAD to inspect what entity types are in the file (Part > Shape Info). If you see only edges and vertices, no closed shells, the file is intentionally wire-only.
• Units mismatch causing geometry below minimum size. If the sender exported in millimeters but omitted the unit declaration, SolidWorks may interpret the values as meters. A 100mm part arrives as 0.1mm — smaller than SolidWorks’ 1e-5m minimum body size threshold, so it’s silently discarded. Check the STEP file for LENGTH_UNIT((),MILLI_,METRE) on the unit line. If that line is absent, the importer uses a fallback — and that fallback may not match the sender’s intent.
• All components suppressed in source. Some assemblies export with components present in the product structure but missing shape geometry because they were suppressed at export time.

Rebuild errors (red exclamation marks) after STEP import

Expected behavior, not a bug. STEP files contain B-rep geometry — no feature history, no parametric relationships. When SolidWorks imports a STEP file and you build new features that reference imported faces, those downstream features will fail if the STEP geometry ever changes.

Treat imported STEP geometry as dumb solids. For predictable sheet metal flat-pattern workflows from imported STEP files, the standard practice is to rebuild the part as native SolidWorks sheet metal rather than using Convert to Sheet Metal on the STEP import.

SolidWorks translation hangs — “Not Responding”

SolidWorks translates STEP in-process on the main UI thread. Very large assemblies (1000+ parts) or assemblies with unresolved lightweight components can block the UI for 5–30 minutes with no progress indicator.

Before exporting large assemblies, resolve all lightweight components: right-click the top assembly in the feature tree and choose Set Resolved. If translation hangs past 30 minutes, end SLDWORKS.EXE, restart, and try exporting from a simplified configuration with non-critical components suppressed.

SolidWorks 2025 SP2 moved large-assembly STEP export to a background thread — the UI stays responsive during translation. If you’re running earlier versions, this is a known limitation, not a system problem.

SolidWorks 2023–2025 STEP export changes

Online STEP Conversion Without SolidWorks Installed

Not every team member who needs a STEP file has SolidWorks installed. Reviewers, procurement teams, and clients sometimes need to convert a SolidWorks file to STEP from a machine with only a browser or a free viewer. Three tools handle this without a SolidWorks license:

Onshape (free account required): Import the .SLDPRT or .SLDASM file into Onshape using Import from the Onshape dashboard. Onshape reads SolidWorks files using its CATIA-heritage geometry kernel, and the re-import frequently resolves geometry that SolidWorks’ own STEP translator has difficulty with — particularly on imported geometry that was repaired inside SolidWorks rather than modeled natively. Once the file is in Onshape, export as STEP via Export, choosing AP214 or AP242 from the format dropdown. One limitation: free Onshape accounts enforce public document visibility. All imported files become publicly searchable. For proprietary designs, use the paid plan or a company-email trial.

CAD Assistant (ODA — free, no account): The Open Design Alliance’s CAD Assistant is a desktop viewer that reads SolidWorks files and exports to STEP, IGES, OBJ, and other formats without any SolidWorks license. The download is free and requires no registration. The STEP output uses the ODA geometry kernel (ACIS-based B-Rep) rather than Parasolid, so the output geometry may differ slightly from SolidWorks’ native export at the B-Rep level. For most fabrication handoffs this is invisible to the machinist or supplier. If your recipient uses automated geometry validation that checks for Parasolid-specific entity patterns, verify the CAD Assistant output before standardizing on it.

GrabCAD Workbench: GrabCAD’s browser-based platform converts SolidWorks files to STEP and other formats as part of its collaboration workflow. A free tier is available. Files uploaded to GrabCAD are stored on Stratasys infrastructure — review your data sensitivity requirements before uploading IP-sensitive designs.

For converting entire assemblies in bulk — or producing consistent STEP files across multiple design revisions — the manual and online methods both hit the same bottleneck: repetition without automation.

When manual export stops being practical

The thirty-second export works once. It doesn’t work when:

• You’re releasing a full product assembly for manufacturing review and need every component exported individually
• You’re running a design revision and need to re-export sixty parts that changed
• Your team has a standard naming convention and metadata structure that needs to be applied consistently across every file
• You’re handing off to a supplier who needs STEP files organized by part number, revision, and material — and they need it by end of day

At that point, the bottleneck isn’t knowledge of the export process. It’s the repetition itself.

The batch export problem

SolidWorks doesn’t have a native batch STEP export tool built into the standard interface. You can write macros using the SolidWorks API, and engineers do — but maintaining custom VBA or C# macros across SolidWorks versions, different configurations, and varying export requirements creates its own maintenance burden.

The alternative is a purpose-built tool that handles batch export without requiring you to write or maintain code. If your team also needs DXF outputs for sheet metal, our batch DXF export guide covers the parallel workflow.

Automating SolidWorks to STEP conversion

This is where CadShift fits into the workflow.

CadShift’s SolidWorks plugin is built specifically for engineers who need repeatable, batch-friendly export jobs. Instead of opening files one at a time and clicking through dialogs, you define your export parameters once — format, output directory, naming conventions, metadata fields — and run the job across as many files as you need.

The plugin handles:

• Batch STEP export across parts and assemblies
• Consistent file naming based on part number, revision, or custom metadata
• Bend line and fabrication metadata for DXF outputs (useful when your workflow includes both flat patterns and 3D geometry handoffs)
• Repeatable job configurations you can run again when designs update

For teams doing regular manufacturing releases, supplier handoffs, or design reviews that require clean STEP packages, eliminating the manual export loop has a real impact on time and error rate. Our ROI analysis breaks down the actual cost savings.

You’re not replacing your engineering judgment — you’re removing the part of the job that doesn’t require it.

Practical tips for cleaner STEP exports

Whether you’re exporting manually or in batch, these habits produce better results:

Fix geometry before exporting. Run a geometry check on every file before the export job. Errors in the SolidWorks model become errors in the STEP file, and they’re harder to diagnose once the file is out of your hands.

Standardize on one STEP variant for your team. Decide whether you’re using AP214 or AP242 and stick to it. Mixed outputs create confusion downstream, especially if recipients are writing import scripts or automating their own intake process. If recipients need DXF, DWG, or IGES instead of STEP, our DWG vs DXF vs STEP vs IGES format comparison covers which format fits each downstream use and where each one loses data.

Name files consistently from the start. STEP files named final_v3_ACTUAL_use_this.stp are a sign of a process that needs structure. If your CAD files have part numbers and revisions in their properties, your export tool should be able to use them automatically. Good version control practices start with consistent naming.

Keep export configurations version-controlled. If you’re using a macro or a batch tool, store the configuration alongside your CAD files. When a supplier asks why the file they received six months ago looks different from the one you sent today, you want to be able to answer that question.

Validate before sending. Open the STEP file in a neutral viewer before it goes out. Takes two minutes and catches the kind of problem that would otherwise surface as a supplier question three days before a deadline.

SolidWorks STEP export: quick reference

Choosing the right approach for your workflow

If you export STEP files occasionally — one-off requests, small assemblies, ad hoc supplier needs — the manual method works fine. Learn the options dialog, pick the right AP variant, validate your output.

If you’re exporting regularly, managing multiple projects, or supporting a team that needs consistent outputs without a manual bottleneck, the manual method becomes a tax on your time that compounds with every release cycle.

The engineers who benefit most from automation aren’t the ones who don’t know how to export STEP files. They’re the ones who know exactly how to do it and are tired of doing it the same way for the hundredth time.

If your team is considering switching CAD platforms entirely, our CAD file migration guide covers how to preserve your STEP workflows during the transition.

Conclusion

Converting SolidWorks files to STEP is straightforward when you understand the format variants, configure the export options correctly, and validate the output before it leaves your hands. The process itself isn’t complicated — the complication comes from scale, consistency, and the expectation that every file in a release package meets the same standard.

For engineers managing high-volume or repeatable export workflows, the question isn’t whether you can export STEP files manually. It’s whether you should be.

If you’re at the point where batch export, consistent naming, and repeatable job configurations would make a real difference in your workflow, learn more at Cadshift.com.