Question 1

Which conversions actually work today?

Accepted Answer

OBJ → GLB, GLTF → GLB, and FBX → GLB are live and run entirely in your browser. Every other pair listed on the site is either on the roadmap (STL and OBJ↔GLTF conversions) or not possible in a browser (anything that exports to FBX — no reliable FBX exporter runs client-side). If a pair isn't Live, the site says so and offers a waitlist instead of pretending to convert.

Question 2

Are my proprietary 3D models safe?

Accepted Answer

Yes. The conversion engine runs entirely on the client side inside your browser. No files are ever sent to a server — your meshes are parsed, transformed, and re-serialized using your own device's CPU and RAM. Closing the tab purges everything from memory.

Question 3

What is the maximum file size supported?

Accepted Answer

150 MB. Files above that are rejected because browser tabs typically have a 2–4 GB memory ceiling and conversion needs several times the input size in RAM. Files over 75 MB will still work but may take a minute. For larger assets, split them in your DCC tool before uploading.

Question 4

Does this support animation data?

Accepted Answer

Partially. OBJ has no animation data by definition. GLTF → GLB preserves any animation tracks and skinned rigs present in the source, since GLB is just a repackaged GLTF. FBX → GLB passes through skinned rigs and animation tracks when they exist, but complex rigs haven't been validated end-to-end — treat animated conversions as best-effort and verify in your target engine.

Question 5

Can I import FBX files? What about exporting to FBX?

Accepted Answer

Import: yes — FBX → GLB is live, so you can drop an FBX and get a GLB back with meshes, materials, and (best-effort) skinned rigs. Export: no — there is no production-quality FBX writer that runs in a browser. Autodesk's FBX SDK is a native C++ library and community JavaScript exporters produce files that fail in Unity, Unreal, and Maya often enough that we won't ship one. If you need FBX output, use a desktop tool like Blender or Autodesk FBX Converter.

Question 6

How can a 3D converter run entirely locally without a server backend?

Accepted Answer

Our pipeline utilizes compiled WebAssembly (Wasm) ports of industry-standard open-source parsing engines, including Assimp and Three.js runtime libraries. When you drop an asset onto the viewport, your browser instantiates a client-side sandboxed virtual environment. The file is read as a raw binary array buffer, reconstructed into a unified scene graph in your local system memory (RAM), and transcoded directly into the target format. Because all compute loops run inside your browser's hardware-accelerated thread, your source files and mesh geometry strings are mathematically incapable of leaving your local machine.

Question 7

Why did my complex file cause the browser tab to crash or reload?

Accepted Answer

Browser-side WebAssembly operates under strict architectural sandboxing limits imposed by modern web engines (typically a maximum memory allocation of 2GB to 4GB per active tab, depending on your operating system). If you attempt to process an un-optimized scene containing millions of polygons, deep high-fidelity draw-call hierarchies, or embedded uncompressed 8K textures, the application may breach the browser's available WebAssembly memory heap, forcing a safe tab reload. For massive production assets, we recommend decimating your high-poly meshes or extracting heavy texture sets before executing client-side transcoding.

Question 8

What happens to my embedded textures, materials, and maps during conversion?

Accepted Answer

When converting to self-contained modern web ecosystem formats like GLTF/GLB or USDZ, our engine attempts to bake standard PBR (Physically Based Rendering) material maps—including Albedo/Diffuse, Roughness, Metallic, and Normal strings—directly into the output file configuration. However, if your source model (such as an OBJ or FBX) relies on absolute external file paths or custom proprietary shaders from offline digital content creation (DCC) tools, the texture paths will break globally. For optimal results, use standard materials and ensure your texture files are structurally embedded or relative to the source mesh.

Question 9

Are skeletal animations, blend shapes, and rig hierarchies preserved?

Accepted Answer

Rigging structures, structural transform hierarchies, joint sets, and basic skeletal animations are fully supported by our core translation layer when moving between robust modern formats (such as FBX to GLB/USDZ). However, certain platform-specific animation features—such as custom animation layers, complex procedural constraints, morph targets, or specialized bezier curve interpolations—may experience translation flattening or parsing discrepancies due to variations in how different target rendering engines interpret skeletal math.

Question 10

Why does my converted model look different in Apple AR Quick Look vs. a web-based glTF viewer?

Accepted Answer

Apple's AR Quick Look environment relies exclusively on the USDZ format, which utilizes a highly specific PBR material framework dictated by Pixar's Hydra rendering architecture. On the other hand, standard web viewers use the glTF standard, which follows a different material schema. Discrepancies in lighting intensity, texture roughness, specular reflection, or alpha-blending transparency are almost always caused by how these two competing rendering engines interpret material channels. We strongly recommend testing your converted files directly in your target engine or runtime environment before deploying them to your live asset production pipeline.

Frequently Asked Questions

Q.01Which conversions actually work today?

Q.02Are my proprietary 3D models safe?

Q.03What is the maximum file size supported?

Q.04Does this support animation data?

Q.05Can I import FBX files? What about exporting to FBX?

Q.06How can a 3D converter run entirely locally without a server backend?

Q.07Why did my complex file cause the browser tab to crash or reload?

Q.08What happens to my embedded textures, materials, and maps during conversion?

Q.09Are skeletal animations, blend shapes, and rig hierarchies preserved?

Q.10Why does my converted model look different in Apple AR Quick Look vs. a web-based glTF viewer?