Quick answer
An STL stores coordinate numbers but does not standardize whether they represent millimeters, inches, or another unit. Do not guess from appearance. Compare one authoritative real-world dimension, identify the intended unit, apply one controlled scale, and record the final millimeter dimensions.
- STL does not carry a standard unit declaration.
- A millimeter–inch mismatch produces a 25.4× linear error.
- Use an authoritative dimension, not an arbitrary slicer auto-scale.
- Scaling also changes clearances, walls, holes, and connector fit.
Why the file cannot answer the unit question
The coordinates in an STL describe relative geometry but carry no standardized unit metadata. The exporting tool and importing tool must agree outside the file. A value of 20 can mean 20 millimeters, 20 inches, or another convention.
3MF can declare its model unit, which is one reason it is safer when scale must travel with the file. Converting to STL removes that explicit declaration, so preserve the source and document the intended dimensions.
Diagnose scale from evidence
- Find one authoritative measurement
Use a drawing, known fastener, build specification, or dimension from the source application.
- Measure the imported model
Compare the same feature and the full bounding box in millimeters.
- Test common ratios
A difference near 25.4 or 0.03937 strongly suggests inch–millimeter disagreement; powers of ten suggest centimeter or meter assumptions.
- Check assembly context
Compare mating parts, stock pins, sockets, and printer envelope before accepting the correction.
- Record the decision
Save the expected and final dimensions with the project so the unit is not guessed again.
Scaling changes more than overall size
- Wall thickness
A 50% scale reduces every wall and feature to half its prior thickness.
- Clearance
Pin and socket gaps scale too, even when the printer’s process error does not.
- Hole diameter
Fastener and drain holes may no longer match their physical purpose.
- Tessellation
Scaling up exposes coarse facets that were less visible at the original size.
- Build volume
Every split candidate and orientation must be recalculated after scale changes.
Make the corrected size explicit
Apply the correction once, avoid stacking transformations across several tools, and export to a new filename that includes the intended scale or dimensions. Reopen the result and confirm its bounding box before splitting, hollowing, adding connectors, or slicing.
Do this in Meshworthy
Verify physical size before geometry operations.
Meshworthy surfaces the model bounding box and scale risks at the start of preflight so repair, splitting, and hollowing are based on the intended final dimensions.
- 01Read the bounding box
Compare X, Y, and Z dimensions with one trusted real-world measurement.
- 02Choose the intended interpretation
Record the source unit and final millimeter size instead of accepting an implicit import guess.
- 03Preview controlled scaling
Review the scale factor and resulting dimensions before applying it.
- 04Invalidate dependent checks
Re-run wall, hole, build-volume, connector, and cavity checks affected by the new size.
- 05Verify the export
Reopen the saved file and confirm the corrected dimensions are baked into the geometry.
Common questions
Technical answers and limitations.
Why is my STL tiny after import?+
The exporter and importer likely assumed different units. Compare a trusted dimension before multiplying the model.
Should I use auto-scale to fit the bed?+
Not for a dimension-critical part. Fitting the bed changes the design size and every mating feature.
Does converting to 3MF restore the missing unit?+
It can store the unit you choose going forward, but it cannot recover an unknown original intent automatically.
Primary references
Verify the underlying guidance.
Apply these checks in Meshworthy
Inspect the model, review the operation, and verify the export.
Meshworthy applies these checks locally on your Mac and does not upload your model.
Check STL scale during preflight ↗