No upload · No account · Runs in your browser
Turn an STL into OBJ, PLY, binary STL, or ASCII STL without handing a client's model to a cloud converter. Everything happens in this tab: no upload, no account, no watermark, and no queue. The download is written straight to your disk by your own browser.
Drop an STL file here
Binary or ASCII input. Choose the output format after the file is measured — the conversion itself is local and instant.
No upload endpoint · no account · no file size cap
Reading locally...
Could not read that file.
Source file
-
Format
-
File size
-
Triangles
-
Bounding box
-
Used for OBJ and PLY only. Lower it for fine detail, raise it for noisy scans.
Choose an STL to begin.
OBJ
The safest hand-off to Blender, ZBrush, CAD, or a render engine. Vertices are merged, faces are indexed, and almost everything imports it.
PLY
A compact ASCII mesh with an explicit vertex/face header. Useful for scan processing, research code, and tools that dislike OBJ.
Binary STL
The normal slicer format: 50 bytes per triangle, small and fast. Re-export it when a converter produced an unnecessarily huge ASCII file.
ASCII STL
Readable and diffable, but several times larger. Useful for debugging a mesh or checking coordinates by eye, not for production.
Cloud converters ask you to upload a model before they will hand back a file. For a commissioned miniature, an unreleased product, or a scan of a person, that is a data-sharing decision disguised as a utility. This converter has no upload step at all: the bytes are read from your disk, converted in memory, and written back as a download.
Nothing is stored between visits. There is no account, no history, no server-side copy, and no watermark added to the output. When you close the tab, the mesh is gone.
Formats, welding, units, and what conversion does not fix.
No. The STL is read locally with FileReader, converted in memory, and saved with a Blob download. There is no upload request and no server-side converter. Your model can be confidential and still never leave the machine.
STL input works in both binary and ASCII. You can export OBJ, ASCII PLY, binary STL, or ASCII STL. Binary STL is the smallest and is what most slicers prefer; OBJ and PLY are useful for sculpting, rendering, and scan tools.
Not in this build. This page accepts STL input and exports OBJ, PLY, binary STL, or ASCII STL. If you need the reverse direction, send a note through the feedback form and it will be considered for the next update.
STL stores every triangle with its own three vertices, so shared corners are duplicated. Before writing OBJ or PLY, the converter merges vertices that fall within the tolerance - 0.001 mm by default. Raise it for messy scans, lower it for very fine details.
No. Coordinates are copied one-to-one. STL files do not contain units, and this converter does not guess or rescale them. If a model is 25.4 times too small, it was probably authored in inches; fix the scale in the slicer or with the Scale Inspector.
No. Conversion is a format change, not a repair. Open edges, non-manifold geometry, and inconsistent winding survive the round trip. Run the file through the STL Printability Checker before you slice it.
Help me build this properly
Does this actually solve your problem, or not?
I built this to answer one question: what percentage do I type into my slicer. But I don't know if that is where your workflow actually breaks. Tell me what is broken, missing, or just plain useless here. Honest answers, especially negative ones, are worth more to me than anything else you could do on this page.