How should I use the STEP manifest endpoint?

Fetch manifest JSON to pin fixture names, sizes, hashes, and MIME expectations in automated tests.

Why does this format have a category-specific hub?

A category-specific hub keeps assumptions aligned with practical workflows and related format alternatives.

STEP Format Hub

STEP (.step, .stp) files represent CAD product data in ISO 10303 exchange syntax, supporting part geometry, assemblies, and manufacturing handoff. Use sample STEP files to validate CAD importers, assembly exchange, and product-data interoperability across engineering tools.

Coverage Snapshot

CategoryThree-d

Files3

Min Size0.5 KB

Max Size1.5 KB

Downloads (30d)13

Primary MIME Signals

model/step

Open Sample Page Open Manifest JSON

Related Formats in Three-d

OBJ (7) STL (7) FBX (4) GLTF (4) 3MF (3) DXF (3) GLB (3) PLY (3)

Format Strategy Links

Open STEP FAQ

Implementation Notes

Use the manifest endpoint for deterministic fixture selection in CI, then validate MIME/type detection against actual parser output.

If this format appears in multiple categories, prefer category-specific hub pages to keep test assumptions aligned with real usage.