When a converted model looks wrong, the mesh is often still there. The trouble is usually in data the target format cannot store, texture files the converter cannot find, or units the source file never declared.

The short version
- Check what the source contains and what the target can store before converting. A successful export does not mean every property survived.
- Treat STL and OBJ dimensions as unlabelled numbers. Confirm the intended unit rather than trusting the size shown after import.
- Do not convert a textured model to STL if its appearance matters. Do not convert an animated FBX to a format that has no bones.
- Open the converted file in a viewer or its destination app, then check size, appearance, and motion against the source.
Step 1: Diagnose the loss before choosing a converter
I start with a short inventory: does this job need the shape alone, or also color, texture images, a particular physical size, or animation? Those are separate requirements. A converter can preserve the triangles perfectly and still give you the wrong file for the job.
SupaVoxel’s 3D File Converter lets you pick a source-and-target pair and read what that conversion keeps or drops. Its converters run in the browser; the file stays on your device. That makes the pair-specific notes a useful first stop when an export has already gone wrong.

The converter index lets you choose a file pair and check its trade-offs.
Describe the symptom precisely. “No texture” might mean the target format cannot store what you need, or it might mean the source refers to image files that were not supplied. “Too small” points toward units. “Character won’t move” points toward animation support or missing clips. Each problem needs a different fix; repeatedly exporting the same pair will not solve a format mismatch.
Step 2: Check units before you touch the scale slider
STL and OBJ do not declare units. Their coordinates are numbers without an attached millimeter, inch, or meter label. If a slicer reads an STL’s numbers as millimeters, that is an assumption made by the slicer, not a fact stored in the file. A model drawn in meters can therefore appear 1,000 times too small when those coordinates are read as millimeters.
Before converting, ask where the file came from and compare its displayed dimensions with the size the object is supposed to have. For a printable part, check a known dimension such as an enclosure width or a bracket length. For an asset destined for a game or web scene, check its size in the destination environment rather than judging it only by how large it looks on screen.
For an STL meant for a slicer, SupaVoxel’s STL to 3MF converter asks you to identify the STL’s file units and writes the result with millimeters declared. It starts with millimeters, but you can select inches when that is how the part was modeled. An inch-based STL then has its coordinates scaled by 25.4 before the 3MF is written. The page shows the expected output size, so inspect that number before downloading.

The unit choice and output-size check help catch a scale error before it reaches the slicer.
The converter also welds matching triangle corners into shared vertices and places the object at the origin, resting on z = 0. Those changes are useful, but they are not a substitute for checking the source mesh. It does not repair holes merely because the result is a 3MF. Once the dimensions look right, share the correctly scaled file rather than passing along the ambiguous STL and asking the next person to repeat your scale adjustment.
Step 3: Trace where the appearance went
A missing color is not always a broken conversion. STL stores geometry, not color or textures, so converting a textured model to STL discards its appearance by design. Converting that STL onward to 3MF cannot recover the missing information. The resulting 3MF can hold color, but this converter has no color in the source to put there; you can assign or paint it later in a slicer.
If appearance matters, check whether the source file actually contains the images or only references them. An FBX, for example, may point to external texture files. If those files are missing during conversion, changing the output extension will not make them appear. Supply the images with the source when the converter calls for them, and inspect the result afterward.
There is another, subtler failure: the images survive, but the surface looks different. FBX files commonly use Phong or Lambert materials; glTF uses physically based metallic-roughness materials. A conversion can retain colors and textures while approximating the original highlights. If a shiny part looks flat, inspect the destination material settings before concluding that its texture was dropped.
I separate these checks in order: is color supported by the target, were the image files available, and does the destination interpret the material as intended? That sequence is faster than trying random export settings.
Step 4: Keep animation only when the target can hold it
A rig is more than a visible mesh. A moving character needs its skeleton, skin weights, and animation clips to travel with the geometry. STL, OBJ, and 3MF do not carry bones, so they are poor targets when the motion itself is part of the deliverable. GLB can carry skeletons, skinning, morph targets, and animation clips.
SupaVoxel’s FBX to GLB converter is intended for this kind of transfer. Its panel reports the animation clips found in the FBX, and the conversion keeps the skeleton and skin weights. Embedded textures can be packed into the GLB; if the FBX uses external images, supply those alongside it or in a zip of the folder. The converter also changes FBX centimeter coordinates to glTF meters, with a file-unit setting for sources made in other units.

The FBX conversion panel identifies content to check, including textures and animation clips.
There is a limit to what “keeps the rig” means. IK solvers, constraints, and custom rig-building properties do not become equivalent glTF features. Bake the motion to keyframes in your animation software before export if it depends on those controls. After conversion, play the clips in the destination app. Seeing the character in a static preview proves only that the mesh arrived.
Step 5: Verify the file you will actually use
Treat the downloaded file as an output to inspect, not proof that the task is finished. Open it in a viewer or in the slicer, engine, or app where it will be used. Check the dimensions first. Then look for missing color, unexpected flat materials, displaced parts, or a character that loads without its motion. For a print, also inspect whether the mesh itself is suitable for slicing; changing formats does not make a flawed surface sound.
If a check fails, go back to the earliest point where the needed information existed. A lost texture may require the original images. A scale error may require identifying the source unit. Missing animation may require a different target format or baked motion. Converting the already damaged output again cannot recreate data it no longer contains.
The destination matters during this final check. SupaVoxel’s Use Cases guides cover paths into printers, game engines, and AR, including the target app’s settings and limits. Use the relevant workflow to check the file in context, rather than stopping when a generic viewer displays a plausible shape. The right conversion is the one that preserves the data your next step actually needs.
FAQ
Why is my converted model tiny?
Check whether the source declares units. STL and OBJ do not, so a destination may interpret their coordinates differently from the software that created them. Compare a known dimension with the output size before changing scale.
Can converting STL to 3MF restore its colors?
No. STL contains no color information for the converter to carry over. You can add color in a slicer afterward, but you cannot recover the original appearance from the STL alone.
Why does my converted character have no animation?
First check whether the target format supports bones and clips. If it does, confirm that the source contained animation clips and that motion dependent on constraints or IK was baked to keyframes before conversion.