Learn when to use STL, STEP, and 3MF for production-grade additive manufacturing—and how to package controlled, revision-safe datasets that enable PBF build prep, HIP/post-processing, machining, and inspection with minimal supplier ambiguity.
Most engineers learn early that “the printer takes an STL,” but production additive manufacturing (AM) for defense and aerospace is rarely that simple. When you are trying to hit drawing requirements after powder bed fusion (PBF) and post-processing—often including stress relief, hot isostatic pressing (HIP), support removal, heat treat, CNC machining, NDE, and full certification packs—the file format you send can either preserve design intent or quietly destroy it.
This article compares the three formats that show up most in production workflows—STL, STEP, and 3MF—from a print-readiness and supplier-readiness perspective. The goal is not to “pick a winner,” but to help you choose the right format for each phase: quoting, build prep, machining, inspection, and controlled release in regulated environments (ITAR, DFARS, AS9100, NADCAP).
Quick framing: STL is a triangulated surface mesh; STEP is a CAD/solid model exchange; 3MF is a modern container that can store meshes plus metadata. In real production, you often provide more than one file type to control risk and shorten supplier back-and-forth.
In a qualified AM supply chain, the “preferred” file format depends on what the supplier is responsible for delivering and how their digital thread is controlled.
For PBF build preparation (DMLS / SLM): Many machine OEM toolchains and third-party build processors still operate on meshes. That means the supplier may ultimately use an STL-like representation even if you send STEP. However, suppliers increasingly prefer receiving STEP plus a drawing (or model-based definition) because it allows them to regenerate a high-quality mesh internally with known settings and to validate critical surfaces before meshing.
For post-processing and machining: If the supplier is doing finish machining (common in aerospace and defense where as-built surfaces are rarely acceptable), they generally want STEP. CNC programming, 5-axis toolpath generation, datum strategy, and CMM programming all benefit from a true solid model. A mesh-only workflow forces extra reverse engineering steps and increases ambiguity around features that must clean up after machining.
For end-to-end suppliers delivering certified hardware: If the same supplier is building, HIPing, machining, and inspecting, they will often request a controlled dataset: STEP for geometry + drawing for requirements + a mesh (STL or 3MF) only if you have already validated it as representative of design intent.
When 3MF is preferred: 3MF can be attractive when a supplier’s software stack supports it and when you want to pass additional information—units, part orientation intent, build items, multiple bodies, and sometimes process notes—without losing track of what belongs together. In practice, 3MF adoption is growing faster in polymer AM than in metal PBF, but metal suppliers are increasingly willing to accept it as part of an RFQ package, especially for complex assemblies or multiple configurations.
Procurement reality: The fastest RFQs come from packages that remove ambiguity. For most defense/aerospace metal PBF programs, a strong baseline is: STEP (authoritative geometry) + PDF drawing (authoritative requirements) + an optional STL/3MF for visualization or quick buildability checks.
Tolerance problems in AM often start before the powder is even loaded: a poor export can unintentionally change geometry, which then flows downstream into build prep, HIP, machining stock decisions, and inspection results.
STL: mesh approximation and the “hidden tolerance stack”
STL represents the surface as triangles. The export uses a chord height / deviation setting and angular tolerance. If these settings are too loose, circles become polygons, fillets flatten, and small features can disappear or distort. Even if your CAD model meets a tight profile tolerance, the STL can violate it before the first build.
For production parts with tight datums, sealing features, thin walls, or critical blend radii, STL must be generated with explicit, reviewed settings. As a practical rule, set mesh deviation tighter than your functional tolerance (and tighter than your intended machining allowance on critical surfaces). Then inspect the mesh: check hole roundness, edge definition, and thin-feature continuity.
STEP: preserves design intent for solids and surfaces
STEP (commonly AP203/AP214/AP242) carries analytic geometry—true cylinders, cones, splines, and topology. That means your supplier can create their own mesh tuned to their machine, layer thickness, and support strategy. STEP also supports better interoperability for downstream machining and inspection.
3MF: mesh-based but typically higher integrity than STL
3MF is still mesh geometry in most implementations, but it typically includes units and can store multiple components in one package without losing alignment. Many STL problems in quoting come from missing unit information (inch vs mm) and “which file is the latest.” 3MF helps, but it does not magically fix a low-resolution mesh.
AM + HIP + machining: plan the geometry for the full route
In metal PBF, you rarely accept as-built dimensions. A common route is: PBF build → stress relief → support removal → HIP (or PM-HIP densification for powder metallurgy routes) → heat treat if applicable → finish machining → inspection.
Each step has implications for how you communicate tolerances and stock:
1) As-built capability: Use the supplier’s demonstrated process capability for PBF (feature size, wall thickness, flatness trends, distortion risk). Do not assign tight tolerances to as-built surfaces unless you have qualification data.
2) HIP effects: HIP improves density and can close internal porosity, but it can slightly change dimensions and relieve residual stress differently than stress relief alone. If critical dimensions are post-HIP machined, this is manageable; if not, you need a realistic dimensional plan.
3) Machining allowance: Identify where machining stock is required and how much. On thin features, too much stock can cause warping or insufficient support during machining; too little stock risks incomplete cleanup. STEP is the cleanest way to define these surfaces; if you must use a mesh, clearly indicate stock strategy in the drawing and RFQ notes.
4) Inspection strategy: For aerospace/defense, inspection often includes CMM, surface roughness checks, and sometimes CT scanning or other NDE depending on criticality. A solid model (STEP) improves CMM programming and comparison, while a mesh can complicate nominal-to-actual alignment.
In regulated manufacturing, the “file format” question is also a configuration management question. The supplier must know exactly what revision is being built, and you must be able to prove it later during an audit or investigation.
STL’s limitation: STL has essentially no robust, standardized metadata. You can name the file “Part123_RevC.stl,” but the format does not inherently carry revision, units, material, or approval status. This is why STL-only packages often cause RFQ delays: suppliers must request clarification or accept risk.
STEP’s advantage: STEP can carry richer product structure, attributes, and in AP242 can support PMI (product manufacturing information) in model-based definition workflows. Even if you are not fully MBD, STEP still helps with consistent geometry exchange and can be tied into PLM and release processes.
3MF’s intent: 3MF was designed as a more complete “manufacturing packet” than STL. It commonly stores units and can bundle multiple parts. Depending on the toolchain, it can also include color, texture, and build item data. For metal production parts, the biggest practical benefits are units and packaging coherence (fewer mismatched files).
Revision control best practice for defense/aerospace:
1) Define the authority: State whether the authoritative definition is the drawing, the STEP model, or a controlled MBD dataset. Many programs still use the drawing as the legal authority, with STEP as a derived reference.
2) Use controlled release and access: If the program is ITAR-controlled, ensure files are distributed through an ITAR-compliant method, with access restricted to authorized persons. Track who received what revision and when.
3) Lock the dataset for the build: For production, suppliers should run a controlled traveler that references the exact file revision(s) and any build processor version/parameter set used. If you are the buyer, ask for this in the build record and certification pack expectations.
4) Tie files to material traceability: Geometry control is only half the story. Production AM requires powder lot traceability, machine/parameter traceability, and post-processing records (HIP cycle charts, heat treat, machining router). Align file revisions with those records to support DFARS flowdowns and customer audit expectations.
Most “AM file problems” are export and translation issues, not design issues. Catching these before an RFQ saves days to weeks.
1) Unit mistakes (inch vs mm)
STL does not store units; the receiving software guesses. A 1-inch part becomes 25.4 inches (or vice versa). 3MF typically stores units, and STEP reliably conveys scale. If you must use STL, specify units in the RFQ and in the filename, and include a reference dimension in the drawing.
2) Coarse triangulation and faceting
Loose mesh settings produce faceted cylinders and “flat” fillets. This can be catastrophic for sealing diameters, bearing fits, or aerodynamic surfaces. Always review the STL/3MF visually and with measurement tools; do not assume the CAD export is correct.
3) Non-manifold edges and open shells
Meshes can contain holes, self-intersections, inverted normals, or non-manifold geometry that breaks slicing/support generation. Run mesh repair checks before sending, or rely on your supplier to regenerate the mesh from STEP.
4) Thin features below process capability
A STEP model may include walls or pins that are below the minimum stable feature size for your alloy and machine. If you export to STL, those features might disappear entirely. Validate minimum wall thickness and minimum hole sizes for your intended PBF process (and consider how HIP and machining will affect them).
5) Exporting assemblies incorrectly
STEP assemblies can arrive with broken references or suppressed components, and STL exports can merge bodies unintentionally. If you are quoting multiple parts or a family of parts, make sure the supplier can clearly identify each item, quantity, and revision.
6) Misleading “watertight” but incorrect geometry
A mesh can be watertight yet still wrong: missing small chamfers, altered fillet radii, or distorted mating faces. This is one of the strongest arguments for providing STEP as the authoritative geometry.
Print readiness is not just “can it slice.” For production, it is a controlled handoff that enables the supplier to create a stable build, plan post-processing, and verify requirements without guesswork. The following steps mirror how successful defense/aerospace manufacturers prepare datasets.
Step 1: Decide what is authoritative
If you use drawings as the contractual authority (common), ensure the drawing fully defines datums, GD&T, finishes, and inspection notes. If you use MBD, ensure PMI is complete and readable in the supplier’s software. State this clearly in the RFQ.
Step 2: Provide STEP for geometry, unless there is a specific reason not to
Send STEP (preferably AP242 when possible) as the primary geometry exchange. This supports buildability review, machining planning, and CMM programming. Even if the supplier will print from a mesh, STEP lets them create the mesh themselves with controlled settings.
Step 3: If providing STL/3MF, control the mesh quality
Use explicit export parameters and document them internally. Then verify:
• Feature check: Critical holes, slots, threads (if modeled), thin ribs, and blend radii are present and dimensionally consistent.
• Surface check: No unexpected faceting on critical surfaces; no flipped normals; no holes.
• Scale check: Confirm units in the receiving viewer/slicer match expectation.
Step 4: Identify AM-specific requirements early
Include notes (in the drawing and/or RFQ requirements) for:
• Material and spec: Alloy, powder specification if required, and any customer-specific requirements.
• Process: PBF type (DMLS/SLM), parameter set control expectations, and whether the supplier must use qualified builds.
• Post-processing route: Stress relief, HIP (and whether HIP is mandatory), heat treat, surface finishing, and machining requirements.
• Inspection/NDE: CMM, dye penetrant, CT scanning, or other NDE expectations; any NADCAP constraints for special processes.
Step 5: Define datum and machining strategy
For hybrid manufacturing (AM + CNC machining), ambiguous datums are a major cost and schedule driver. Provide clear datum features and indicate which surfaces will be machined. If you have a preferred fixturing or orientation intent (for distortion control), communicate it as guidance—but allow the supplier to propose alternatives that improve yield.
Step 6: Plan for support removal and accessibility
A design can be printable but not producible if supports cannot be removed or if critical internal passages cannot be inspected. Include access notes where relevant, and consider CT scanning requirements if internal features are mission-critical.
Step 7: Align acceptance criteria to realistic capability
Be explicit about which characteristics are critical-to-function and which are cosmetic. For example, specify surface roughness requirements only where needed, and understand that as-built PBF surfaces often require machining or secondary finishing to meet tight Ra values.
A strong RFQ package reduces supplier assumptions, improves quote comparability, and shortens the time to first-article success. In defense and aerospace, it also supports compliance and auditability.
Recommended RFQ contents (practical checklist):
1) Geometry files
• STEP (preferred): Authoritative geometry for manufacturing planning.
• STL or 3MF (optional): For quick printability review, quoting, or when you need to communicate a specific mesh (e.g., scanned data). If included, label it as “reference” unless it is contractually controlled.
2) Drawing / requirements document
Include GD&T, datums, surface finish, heat treat/HIP notes, marking, and acceptance criteria. Clearly state drawing revision and any deviation from standard notes for AM parts (e.g., as-built surfaces permitted in non-critical zones).
3) Statement of work (SOW) for the manufacturing route
Define what the supplier is responsible for: printing only, or printing + HIP + machining + inspection. If HIP is required, specify whether it is standard or requires customer-unique cycles, and whether the supplier must provide HIP charts.
4) Material and traceability requirements
State powder requirements (supplier-approved powder list if applicable), heat/lot traceability expectations, and the required documentation: certificates of conformance (CoC), material test reports, and build record content. If DFARS or customer flowdowns apply, list them explicitly.
5) Quality system and special process requirements
For aerospace/defense, include expectations such as AS9100 certification, NADCAP for relevant special processes, calibration requirements, and inspection record retention. If ITAR applies, state it and require confirmation of compliance.
6) Inspection plan expectations
Indicate which dimensions are key characteristics, what measurement methods are acceptable (CMM vs manual), and whether CT scanning/NDE is required. Define first article inspection (FAI) requirements (e.g., AS9102 format if needed) and what must be included in the certification pack.
7) Revision and configuration control
Provide a controlled revision list and specify how changes will be communicated. Require the supplier to reference the exact revision(s) on travelers, CoCs, and inspection reports.
How to think about STL vs STEP vs 3MF in the RFQ:
• Use STEP to communicate design intent, enable machining/inspection, and reduce geometric ambiguity.
• Use STL when you need maximum compatibility, but treat it as a derived artifact that must be verified and controlled.
• Use 3MF when your workflow benefits from bundled files and units/metadata, and your supplier’s toolchain supports it—especially for multi-part quoting packages.
Ultimately, the best “3D printing file formats” strategy is the one that preserves design intent from CAD through PBF, HIP, machining, and inspection while supporting controlled release and traceability. In production AM, the file is not just a shape—it is the first step in a regulated manufacturing record.
Define a single contractual authority at RFQ/release. If your organization controls requirements via 2D drawings, treat the drawing as authoritative and use STEP as a derived geometry reference for build prep and machining. If you are running model-based definition, release an AP242 STEP with complete PMI as the authoritative dataset and ensure the supplier can read the PMI in their inspection/CAM stack. In all cases, state the authority explicitly in the PO/SOW and require the supplier’s traveler, inspection reports, and CoC to reference the exact released dataset revision.
Include (1) units explicitly in the RFQ notes and filename (especially for STL), (2) part number and revision in the file name and on the drawing/model properties, (3) a reference dimension or gauge feature on the drawing for quick scale verification, and (4) a revision-controlled file list that identifies which files are authoritative vs reference. If a mesh is intended to be used for manufacturing, also document the mesh export settings (chord height/deviation and angular tolerance) and require the supplier to confirm they used the specified file revision in the build record.
Provide a clear product structure: a BOM with line items, quantities, and revisions, plus a STEP assembly that matches the BOM. Include unique identifiers for each body/part and avoid suppressed components or ambiguous configurations. If the build includes multiple variants, separate them into distinct, revision-controlled packages. Require the supplier to acknowledge the received file list and to call out any translation issues (missing references, merged bodies, or coordinate shifts) before finalizing the quote or locking the build traveler.
Our team of experts is ready to help you find the right materials and manufacturing solutions for your project.