Starter
3credits
$7.99
$2.66 each
3 downloads of any size. Good for a one-off project.
Convert an OBJ (.obj) polygon mesh to STEP (.step or .stp) for CAD import, engineering review and supplier handoff. The result represents the OBJ geometry in a STEP-compatible form; it does not recreate parametric features, smooth analytic surfaces, materials, textures or the original design history.
Choose one OBJ file. This page is already configured to create STEP output.
Drag and drop your OBJ mesh here
or choose a file from your computer
Browse filesMaximum file size: 300 MB
Files under 5 MB convert and download free. Larger files use one credit for one completed download, regardless of file size.
Pricing
Files under 5 MB convert and download free. Larger files use one credit for one completed download, regardless of file size. 1 credit downloads any file, any size, and credits never expire.
Starter
3credits
$7.99
$2.66 each
3 downloads of any size. Good for a one-off project.
Pro
5credits
$12.99
$2.60 each
5 downloads of any size. The everyday choice.
Team
10credits
$19.99
$2.00 each
10 downloads of any size. Best balance of price and volume.
Studio
15credits
$26.99
$1.80 each
15 downloads of any size. Lowest price per file.
Start the OBJ-to-STEP workflow in your browser without installing a CAD application or conversion plugin.
Move the visible polygon shape into a STEP workflow without claiming that mesh data becomes a native parametric CAD model.
Open the STEP result in the target CAD application and check scale, surface or body status, face count and whether separate OBJ objects were retained.
Open STEP viewerConversion files stay private, are not added to the public CAD library and are automatically deleted within 7 days.
Continue your workflow
Inspect the OBJ and its companion assets, validate the STEP geometry and request a native rebuild when editable engineering features are required.
Simple conversion workflow
Move from a polygonal OBJ mesh to a STEP-compatible CAD exchange file in three steps.
Choose one .obj file up to 300 MB. Use a closed, manifold mesh with consistent normals for the most reliable geometric result.
The route is preconfigured for STEP output. Start the conversion without searching through a destination-format menu.
Open the .step or .stp result in the receiving CAD tool. Verify units, face count, body status, separate parts and critical dimensions.
Format behaviour
OBJ stores polygon vertices, faces, normals, UV coordinates and optional object or group names; materials are usually referenced through a separate .mtl file and external textures. STEP is built for CAD exchange. Conversion translates the polygon geometry into a faceted STEP-compatible representation, but it cannot infer original sketches, features or smooth analytic surfaces.
Wavefront OBJOBJ
STEP modelSTEPFormat comparison
Choose the format according to what the next application needs—not because one is universally better.
| Feature | OBJ OBJ | STEP STEP |
|---|---|---|
| Primary use | 3D assets, rendering and polygon modelling | Neutral CAD exchange and engineering handoff |
| Geometry | Polygon mesh | B-rep or faceted geometry in a STEP container |
| Visual data | Can reference MTL materials, textures and UVs | Not designed to carry OBJ texture packages |
| Editability | Mesh and vertex editing | CAD operations may be possible, but no recovered parametric feature tree |
| Units and structure | No universal unit convention; objects and groups supported | Explicit units and product structure are possible, but depend on conversion support |
A CAD application or supplier specifically requires STEP
You need the visible mesh shape inside a CAD exchange workflow
Materials and textures are not required in the destination
A faceted, non-parametric result is acceptable
The next step is rendering, animation or game-engine use
Textures, UVs, materials or smoothing information matter
You are still editing polygon topology
The receiving tool already accepts OBJ
Before continuing
A STEP file can open successfully while still being faceted, incorrectly scaled or missing visual and object data. Validate the engineering result.
OBJ has no universal unit convention. Measure a known feature and apply the intended scale in the STEP workflow.
Check how the target CAD application classifies the converted geometry.
Dense OBJ meshes may create a heavy STEP with thousands of small faces.
Confirm whether OBJ objects, groups or connected shells remained separate where required.
Inspect normals, gaps, non-manifold edges and self-intersections inherited from the OBJ.
Retain the original OBJ, MTL and texture files because STEP normally will not preserve the rendered appearance.
Common problems
Most issues are caused by mesh defects, undocumented units, dense topology or expecting rendering data and CAD features to survive the conversion.
Cause: The output follows the OBJ polygons.
Fix: Reduce unnecessary mesh density or request a native surface rebuild when smooth analytic faces are needed.Cause: OBJ visual data lives in MTL and texture files that do not map to this STEP workflow.
Fix: Keep the original visual asset package and use STEP only for geometry exchange.Cause: OBJ does not enforce a standard unit.
Fix: Confirm the authoring unit and rescale in the receiving CAD tool.Cause: The OBJ is not watertight or contains invalid topology.
Fix: Repair holes, non-manifold edges and self-intersections before retrying.Cause: A high polygon count can generate thousands of STEP faces.
Fix: Decimate a copy while protecting critical dimensions.Cause: Conversion did not create sketches, constraints or native features.
Fix: Commission a clean parametric rebuild for design changes.Secure processing
Engineering files can contain confidential product geometry and documentation. Marathon OS keeps conversion uploads separate from its public CAD library and explains how each file is handled.
Files are transferred over an encrypted connection.
Uploaded source files and converted outputs are automatically deleted within 7 days.
Uploading or converting a file does not transfer ownership of the design to Marathon OS.
Conversion files are not listed in the public Marathon OS CAD library.
Explore a small set of adjacent engineering, mesh and drawing handoffs.
CAD to 3D-printing mesh
Legacy surfaces to modern CAD exchange
Mesh to CAD exchange
Mesh handoff for slicing
Rhino to CAD/CAM exchange
Drawing exchange
Marathon OS Design Hub
Search the Marathon OS library for a usable starting model. Review dimensions, licensing and manufacturing suitability before using a downloaded file.
Frequently asked questions
Clear answers about output behaviour, compatibility, pricing, file limits and privacy.
Upload the OBJ file (.obj), confirm STEP as the preselected output, start the conversion and download the STEP result (.step, .stp). Verify it in the application used for the next workflow.
Use OBJ-to-STEP when a CAD, manufacturing or supplier workflow requires STEP and only the polygonal OBJ geometry—not its rendered appearance—needs to be exchanged.
No. The STEP result is derived from the OBJ polygons. It does not recreate sketches, constraints, dimensions or native features, and it may remain a faceted shell or surface model.
This route accepts .obj input and creates .step, .stp output.
Files under 5 MB can be converted and downloaded free. Larger files use one credit for one completed download.
You can upload a OBJ file up to 300 MB. Dense meshes can produce large STEP files with many faces and slow CAD performance.
Files are transferred securely, are not published to the public CAD library and are automatically deleted within 7 days. You retain ownership of the uploaded design.