Batch-Export STEP from SolidWorks (and Convert Them All at Once)
You have a folder of 50, 200, or 2,000 SolidWorks parts and assemblies, and you need STEP files out of all of them -- for a supplier, a PLM handoff, or a downstream conversion to STL or glTF. You open File > Save As, pick STEP, click through the export dialog, and repeat. And repeat.
Step 1
SolidWorksSave As STEP: by macro, PDM rule or by hand.Step 2
STEPA neutral, ISO-standard file. No SolidWorks seat needed to read it.Step 3
STL · glTFConvert the whole folder to STL, OBJ, 3MF or glTF in one pass.SolidWorks has no built-in bulk STEP export. The Save As dialog exports exactly one open document at a time. There is no folder-level 'Export All' command, no right-click-in-Explorer batch option, and no setting in Options that turns Save As into a loop. This has been true across recent SolidWorks releases -- if a future version adds native bulk export, it will show up as a dedicated menu item, not a checkbox buried in export settings.
Three ways to batch-export STEP from SolidWorks
Which route makes sense depends on how many files you have, whether they're under PDM control, and whether you're comfortable running a macro.
| Route | Best for | Setup |
|---|---|---|
| 1. A VBA/API macro that loops over a folder | Big folders. Free, in any edition with the API. | Paste a VBA macro once, then run it per project. |
| 2. SOLIDWORKS PDM export / transition rules | Vaulted files, exported on each state change. | Needs PDM. Configure the transition once. |
| 3. Manual Save As loop (for small batches) | Under a dozen files. | None. |
1. A VBA/API macro that loops over a folder
The most common approach: a SolidWorks VBA macro that opens each part or assembly in a target folder, calls SaveAs3 with the STEP format flag, and closes the document, moving to the next file. Public macro libraries (SolidWorks forums, CodeStack, Blue Byte Systems) publish ready-to-run versions of this pattern, including variants that export every configuration of a multi-config part as a separate STEP file.
You control the AP schema (AP203 vs AP214 vs AP242) via a constant in the macro, and the output folder and file naming are usually parameterized at the top of the script. This is free and works in any SolidWorks edition with the API enabled, but it does require someone comfortable pasting VBA into the macro editor and running it once per project or on a schedule.
2. SOLIDWORKS PDM export / transition rules
If your files live in a SOLIDWORKS PDM vault, PDM can be configured to automatically generate a STEP (or other neutral format) export whenever a file transitions to a specific state -- for example, moving from 'In Work' to 'Released'. This is the cleanest option for teams that already have PDM, because it requires no manual step at all once configured.
- Add a 'Convert Task' or export add-in to the relevant workflow transition
- Point it at a STEP export template with your preferred AP schema
- Every file that reaches that state gets a STEP export automatically, no manual batch run needed
The tradeoff is setup cost and needing PDM in the first place -- not a fit if you're a small shop working from local files.
3. Manual Save As loop (for small batches)
For a handful of files -- under a dozen or so -- it is often faster to just open each one and Save As STEP manually than to write or find a macro. Not elegant, but zero setup time. If you find yourself doing this every week, that's the signal to invest the hour in setting up route 1 or 2 instead.
Once you have STEP files: batch-convert to anything else
Point the batch mode at the folder of STEP exports and convert the entire set to STL, OBJ, 3MF, glTF/GLB, PLY, FBX, DAE, or another target format in one pass, with consistent tessellation quality and unit settings across every file. From the CLI:
cadconvert batch -i ./step-exports -o ./stl -f stl -r
cadconvert batch -i ./step-exports -o ./gltf -f gltf -rBoth commands recurse into subfolders (-r) and preserve the source folder structure in the output by default, so a nested export tree from route 1 or 2 above converts cleanly without manual re-sorting.
Learn more: More on converting SolidWorks files · Full CLI & batch automation reference
Batch-convert your STEP exports todayDownload the free trial: 10 conversions with every feature. Convert an entire folder of STEP files to STL, OBJ, 3MF or glTF in one pass, with no subscription and no cloud upload.
Download Free TrialWhy the downstream conversion needs no SolidWorks license
STEP is a neutral, ISO-standardized exchange format -- once your parts are exported to it, no tool needs a Dassault SDK or SolidWorks seat to read them. 3D CAD Converter reads STEP with its own CAD kernel, entirely independent of SolidWorks.
That matters for teams handing files to 3D printing services, game studios, or manufacturing partners who don't have (and shouldn't need to buy) a SolidWorks license just to open geometry someone else designed.
Frequently Asked Questions
Does SolidWorks have a built-in bulk STEP export?
No. Save As exports one document at a time. Bulk export requires a VBA/API macro that loops over a folder, SOLIDWORKS PDM export/transition rules if your files are vaulted, or a manual Save As loop for very small batches.
Can 3D CAD Converter open my native .sldprt or .sldasm files directly?
No. Like any third-party tool without the Dassault SDK, it cannot read native SolidWorks files. Export STEP or IGES from SolidWorks first, then convert that neutral file -- the standard CAD interoperability workflow.
How do I convert a whole folder of exported STEP files to STL or glTF at once?
Use 3D CAD Converter's batch mode, or run cadconvert batch -i ./step-exports -o ./stl -f stl -r from the command line. It converts every file in the folder (and subfolders, with -r) in one pass with consistent settings.
Do I need a SolidWorks license to convert the exported files?
No. Once the STEP or IGES file exists, converting it further to STL, OBJ, 3MF, glTF and more requires no SolidWorks license -- useful for sharing with partners who only need the neutral files and a converter.