Yes: send an STL when you want pricing on the exact printable geometry you already trust. Send a STEP file when the part may still need edits, fit changes, or feature cleanup before release. Send both when you have them, because that gives a serious shop the fastest route to quoting the current part without boxing the job into mesh-only revision pain later.
The mistake buyers make is treating file type like a tiny technical preference. It is not. File choice changes how quickly a shop can quote the job, how cleanly revisions can be handled, and whether a prototype-stage conversation quietly turns into a production-risk problem.
If you are still gathering the whole request, pair this with the full quote-prep guide. If the real blocker is fit, tolerances, or revision control, read the fit and tolerance guide next.
STL: best when the exact print-ready shape is already settled and you mainly need pricing and lead time.
STEP: best when the part may still need dimensional edits, feature cleanup, or shop-side manufacturability review before approval.
Both: usually the strongest move when you want fast quoting now and a cleaner path for revisions, approvals, and future reorders.
What each file type actually does at quote stage
| File type | Best use | Strength | Main risk |
|---|---|---|---|
| STL | Quote the current printable geometry. | Fast for slicing, printability review, and pricing the exact mesh. | Awkward for clean edits, feature changes, and controlled revision work. |
| STEP | Review a part that may still move before release. | Better for CAD edits, feature checks, and production-minded cleanup. | May not reflect the exact mesh you exported or intended to print right now. |
| Both | Quote fast while preserving editability. | Lets the shop compare the printable mesh with the editable source. | Creates confusion if version names are sloppy or the files do not match. |
The buyer decision rule that usually works
- Use STL only when the file is genuinely settled and you want pricing on that exact geometry.
- Use STEP only when the shop mainly needs to review or help refine the design before anyone should treat it as print-ready.
- Use both when the job is commercially real, but you still want clean room for fit corrections, revision control, and sample-stage learning.
That last case is common. A lot of buyers say a part is final when what they really mean is we want to start pricing the current version. Those are not the same thing.
When an STL is enough
An STL is usually enough when:
- the part is already print-ready
- you do not expect geometry changes after quoting
- the main goal is price and lead-time feedback on the current shape
- the fit is forgiving or already proven
- you are not asking the shop to repair CAD intent through the quote process
This is common for straightforward brackets, covers, spacers, adapters, organizers, and already-proven replacement parts.
When a STEP file is the better move
A STEP file earns its keep when the part is not really frozen yet.
- critical dimensions may still move
- mating features need a cleaner review
- hole sizes, bosses, slots, or wall thicknesses may still need adjustment
- the job may move from one sample into a repeatable production version
- you want the shop to flag manufacturability issues before treating the geometry as released
If the design is still learning, forcing everything through STL can make the quote happen faster but the next step messier.
Why serious buyers often send both
Sending both is not overkill. It is often the most practical buyer move.
- the STL shows the exact mesh you are currently asking the shop to evaluate
- the STEP preserves an editable source if fit, tolerance, or feature adjustments show up during review
- the shop can separate price the current part from help clean up the next revision without pretending those are the same job
That is especially useful if the order may become a repeat batch later. Production-minded suppliers care about what is quotable now and what becomes the controlled baseline afterward.
Do not just send files. Send a release packet.
The highest-leverage improvement most buyers can make is not choosing a magic file type. It is packaging the files so the shop knows which one is current and what stage the job is in.
A clean release packet usually includes:
- the current STL
- the matching STEP file, if available
- a simple revision label such as Bracket-A_Rev-B
- a note stating whether this is prototype pricing, sample approval, or production quoting
- any fit-critical notes or mating-part references
- quantity, material direction, and deadline context
If the files do not match, say so. That is much better than making the shop guess which one is authoritative.
What JC Print Farm would want clarified before trusting the files
A production-minded supplier should not only ask which file type did you send? The better question is what are we allowed to treat as released?
- Which file is current? If the STL and STEP differ, which one governs?
- Is this prototype or production intent? A learning run and a repeatable batch are not the same commercial job.
- Can dimensions still move? If yes, the quote should not be treated like a locked release.
- What is fit-critical? Holes, snaps, insert pockets, and mating faces need more context than the rest of the model.
- What should reorders match? That answer matters if this turns into a repeat job later.
That is the difference between generic shop talk and real operator guidance. JC Print Farm should feel like the place you talk to when the files need to survive quoting, approval, and repeat production without turning every order into a reset.
Common buyer mistakes
Sending only an STL for a part that still needs edits
If the design may still change, mesh-only handoff creates avoidable friction. The quote might still be possible, but revision handling gets uglier fast.
Sending both files with no version control
Two files are not helpful if the shop has to guess whether mount-final.step is newer than mount-final2-reallyfinal.stl. File discipline matters more than buyers expect.
Assuming STEP means the shop should redesign the part for free
A STEP file creates a cleaner path for changes. It does not automatically make design work part of the quote. If cleanup or redesign is needed, separate that scope early.
Treating quote-stage files like a production release without saying so
Many buyers ask for pricing on a current version and only later realize they were not ready to lock it. That is normal, but it should be named honestly so no one mistakes exploratory quoting for a controlled release.
How file choice affects quote speed, approval, and reorders
| Stage | What helps most |
|---|---|
| Fast first quote | A clean STL plus quantity, material direction, and deadline. |
| Fit review or revision planning | A STEP file or both files, plus notes on what may still change. |
| Sample approval | A named revision, fit-critical callouts, and clarity on what the approved unit should represent. |
| Repeat production | A controlled baseline that says exactly which file revision future batches should match. |
What to send if you do not have both
If you only have an STL, send it, but say whether the design is truly final. If you only have a STEP file, send it, but explain whether the current CAD represents the intended printable version or still needs cleanup.
If you do not have any real file yet, this is no longer an STL-versus-STEP question. Start with what to do when you do not have an STL or how to package photos, notes, and references for a quote.
A simple file note buyers can reuse
This STL is the current printable geometry for pricing. The matching STEP file is attached for revision control if fit or feature changes are needed. Please quote the current revision as submitted, and flag anything that should be resolved before sample approval or production release.
That short note prevents a lot of avoidable ambiguity.
Bottom line
Send STL when the shape is settled. Send STEP when the design may still move. Send both when you want fast quoting without sacrificing revision control.
The stronger buyer move is not just choosing the right extension. It is making the job stage obvious so the shop knows whether it is pricing a final part, helping with a moving design, or preparing something that may need to hold up through repeat orders later.
If you want pricing on a controlled request package, use quote.jcsfy.com. If the real issue is turning rough file handoff into a production-minded workflow that can survive revisions, approvals, and repeatability, JC Print Farm is the better next conversation.