Convert STL, OBJ, and 3MF With a Defined Output in Mind
Suppose you receive a decorative bird as an OBJ, complete with a colored body and a separate wing, but your printing service requests STL. You need a usable surface file, not a different-looking filename. This guide follows that transfer and the related STL-to-3MF and 3MF-to-STL routes using documented PrusaSlicer 2.9 menus, with version 2.9.4 as a fixed reference. It also explains how to export an OBJ when a recipient requests that mesh format. The central distinction is between transferring geometry and preserving an appearance model or a slicer project. The example uses an illustrative bird body expected to measure 100 millimeters long; substitute a dimension from your own design. You will make separate output files, reopen them, and check what actually crossed the boundary before passing them on.
A: They can reference separate position, texture-coordinate, and normal lists. They are not three physical coordinates for each face corner.
A: One surface position can need different texture coordinates on opposite sides of a seam. An importer may represent those combinations with separate records.
A: Yes. The OBJ convention allows indices relative to the end of the relevant list at that point in the file. A minus sign there is not a negative physical dimension.
A: It is a comment. A descriptive sentence on that line does not add a surface to the printable model.
A: No. Texture coordinates address the image mapping, while position coordinates describe the model geometry. Resizing the model is different from moving its image mapping.
A: OBJ can describe freeform elements as well as polygon faces. A mesh-oriented consumer may not support the authoring application’s curve representation; obtain an evaluated surface export from that application.
A: Micron, millimeter, centimeter, inch, foot, and meter. The model’s declared unit controls interpretation of its coordinates.
A: The core rules prohibit processing that document. Request a supported delivery from the producer.
A: It can contribute, but thumbnails and other package resources also affect the comparison.
A: No. It organizes internal model references; external inventory identification needs a separate part reference.
Choose the Route Before Opening the File
For an OBJ that needs to become a plain printable mesh, use the OBJ-to-STL route below. For an STL that you want to prepare and revisit in PrusaSlicer, save a 3MF project. For a 3MF whose recipient needs only surface geometry, export STL or OBJ from the opened project. These are related operations, but they deliver different kinds of information. A geometry export cannot stand in for a saved preparation project when the recipient needs editable print settings.
The reference application is PrusaSlicer 2.9.4, rather than an unspecified online converter. The paths belong to its documented 2.9 interface; later releases or translations can display different wording. This is a documentation-based walkthrough, not a claim of hands-on testing on every operating system. Download software from its official distribution, and keep your existing design files outside the folder where you will save conversion attempts.
Prepare the Bird and Its Appearance Assets
Place the original OBJ, its MTL material library, and any referenced images together in a source folder. An OBJ can refer to material definitions outside its own geometry text, and those definitions can refer to texture images. The Library of Congress OBJ description explains this relationship; the original Wavefront syntax reference, reproduced in Paul Bourke’s archive, documents the face and texture indices discussed below. Preserve those assets even though the geometry-only route here will not carry their appearance into the final STL.
Write down which physical pieces you expect: one body and one wing in this example. Also obtain a dimension from the designer or the source application, such as the body’s 100-millimeter length. The number is an illustrative target, not a recommended bird size. If you have only a download preview and no dimension, establish the intended size before treating a later import as correctly scaled.
Make a separate output folder and choose descriptive names such as bird-body.stl and bird-preparation.3mf. Keeping the source and derivative apart prevents an accidental overwrite while you explore the menus. It also leaves the original appearance package available if you later need a color-capable workflow. Do not delete an apparently unused image merely because this particular slicer does not display it.
Convert OBJ to STL in Four Actions
First, import the geometry. Start with an empty plate. Choose File > Import > Import STL/3MF/STEP/OBJ/AMF and select the OBJ. The English menu wording is confirmed in the version-tagged application source. If importing produces several entries, inspect which entry corresponds to the bird body rather than assuming the first one is the whole design.
Second, establish the imported size. Select the body and inspect its displayed dimensions in the object manipulation panel. Compare its long dimension with the expected 100 millimeters, allowing for which axis the model occupies. If the result is wrong, resolve the source unit convention before continuing. A tiny object and a very large object can both look plausible when the view automatically frames them.
Third, export the intended model. Right-click the body in the 3D view and choose Export as STL. Save bird-body.stl in the output folder. For a separate wing, repeat the operation on its own model entry if the import exposes it separately. If the imported design remains a single entry containing both pieces, do not pretend that naming the output body-only will isolate one of them; first establish the intended object separation in an appropriate modeling workflow.
Fourth, reopen the output on an empty plate. Import bird-body.stl and compare its silhouette and size with the body you intended to send. The documented export route is in Prusa’s export guide. Its format-support page also states that OBJ materials and textures are ignored during import. The missing colors are therefore an expected limitation of this route, not evidence that the original texture images were corrupt.
Save an Imported STL as a 3MF Project
Import the STL into an empty PrusaSlicer plate and establish the required size before preparing the job. Set up the objects as needed for your actual printer, then choose File > Save Project as and save bird-preparation.3mf. Prusa’s project documentation describes this as saving objects, settings, modifiers, and their parameters. Close that project and reopen the saved 3MF through File > Open Project to check the preparation you intended to retain.
The new file combines imported geometry with preparation work performed in the slicer. It does not reconstruct the original bird’s sculpting layers, CAD constraints, or missing painted feathers. If you subsequently change a print setting, save the project again when you want that change retained. Exporting another STL instead would provide another surface file, not an updated record of the editable preparation.
Extract a Model or a Whole Plate From 3MF
Open the 3MF as a project in PrusaSlicer and inspect the object list. A project can contain the bird, its wing, and other models arranged around them. Decide whether the recipient needs one model or the entire arrangement. That decision determines which export command to use; it should not be left to the recipient to discover by opening an unexpectedly crowded file.
For a single model, use its right-click Export as STL command. For the entire plate, choose File > Export > Export Plate as STL/OBJ and select the requested output format in the save dialog. The whole-plate route writes a geometry handoff of the plate’s models. It does not promise that every separate object, instance relationship, or preparation control will remain independently editable in another application.
Reimport the result into a fresh plate before sending it. If the whole arrangement was intentional, inspect the distances between the bird pieces as well as their dimensions. If only the body was required, verify that the wing and unrelated models are absent. Do this on the saved derivative rather than judging the still-open project, because the project view cannot reveal that the wrong export scope was chosen.
Export OBJ When the Recipient Needs a Mesh in That Format
The same plate-export command provides an OBJ destination, so an imported STL or opened 3MF can become an OBJ geometry delivery. Choose OBJ in the output dialog, save a distinct file, and open it in the receiving application. Treat this route as exporting the mesh that the slicer handles. It is not a texture-authoring workflow, and an OBJ extension does not recreate the MTL assignments ignored on an earlier import. When the recipient needs textured OBJ rather than plain geometry, return to the appearance-authoring application and use its supported material-and-image export route.
Know Which Information Each Output Leaves Behind
The conventional STL derivative carries the triangulated surface used for this handoff. It is suitable when the requested deliverable is the bird’s shape at an agreed size. Surface paint, texture-image references, and editable slicer settings are outside that limited delivery. Sending the original OBJ appearance folder alongside the STL can explain the intended look, but it does not embed that look into the STL itself.
OBJ supports more kinds of information than this slicer route uses. Its ability to express material relationships does not oblige every importer to read them or every exporter to recreate them. This distinction matters if a service requests OBJ for color printing: ask whether it needs geometry only or a complete textured asset. A plain OBJ created here and the original textured OBJ can have the same extension while serving different purposes.
A 3MF is a structured package rather than just a triangle list with a different suffix. The 3MF Core Specification defines model units, objects, and package relationships. PrusaSlicer’s project adds its own preparation information within that ecosystem. Opening the geometry in another program does not establish that the other program has reproduced every application-specific setting.
For the bird, choose between two honest deliveries: a simple body mesh for a recipient preparing its own job, or a PrusaSlicer project for a collaborator continuing that preparation. Keep the appearance source when colored feathers matter. None of these files replaces the native sculpt or CAD document if someone needs to redesign the wing attachment. Mesh conversion transfers an available representation; it does not reverse the design process.
Resolve Units With a Known Dimension
Use the 100-millimeter body as an arithmetic check, not as a visual judgment. If the source author intended inches but the numeric coordinates are interpreted as millimeters, the discrepancy has a recognizable cause. The 2.9 interface includes File > Import > Import STL (Imperial Units) for an imperial STL. Use that route only when the source convention is actually known, rather than trying it because an object looks small.
For another mismatch, identify the source unit and the application’s current interpretation before changing size. After any correction, export, reopen, and compare the same body dimension again. Also compare the wing with its mating region, because fixing one selected model while leaving another unchanged creates a new assembly problem. Once both pieces have the intended relationship, avoid applying another conversion factor merely because the recipient uses a different display unit.
Keep Separation and Placement as Different Requirements
Two bird pieces can be correctly sized yet no longer occupy a useful relative position. Individually exported models may be placed separately by the next slicer, while a plate-wide export can carry an arrangement intended only for printing. Tell the recipient whether the wing is a separate printable piece or is shown in its assembled position. Those are different relationships even when the underlying surfaces are identical. If assembled placement matters, approve that relationship in the receiving application rather than relying on the filename to communicate it.
Finish With the File the Recipient Will Actually Use
Open the delivered derivative from its output folder, not a cached source tab. For the single-body request, the acceptance check is concrete: the body is present, the wing is absent, and the expected long dimension remains 100 millimeters. For a two-piece delivery, check both pieces and the stated placement convention. This small inspection directly tests the selected export scope instead of adding a general approval form around it.
Then prepare the actual job in the intended slicer. Examine the wing attachment and the bird’s thin features where an export or unsupported geometric operation could affect the manufactured shape. This is not a reason to repeat repairs until every warning disappears; investigate the particular feature that changed. If the derivative differs unexpectedly, return to the last correct representation and identify the operation responsible.
Deliver only the files needed for the agreed purpose, with a short statement such as: body mesh, 100 millimeters long, plain geometry; wing supplied separately. Include the appearance assets when the recipient has explicitly requested that richer source. Keep the preparation project for future changes to the printing setup. The completed conversion should let the next person begin the intended operation without guessing which information you meant to preserve.
