3D Converter

Keeping OBJ/glTF dependencies named so MTL, BIN, and texture references resolve is exactly the kind of detail that prevents a successful conversion from looking broken later. The before-and-after reports and re-parsing check should make handoffs safer; could you add an option to package the converted output and its referenced textures into one downloadable archive? It would help when moving assets between a modeling tool and a web project.

Rejecting files with no renderable triangles before export is a nice touch, most converters fail silently there. How do you handle large meshes in the browser? We convert video files client side and the main problem was memory: big files crashed the tab until we stopped loading everything at once. Is there a size limit, or do you process in chunks?

Converting OBJ/glTF locally in the browser instead of uploading files is a real win for anyone handling client IP. The route-aware options (normal recalculation, unit handling, axis transforms) are exactly where cheap converters silently break meshes, so surfacing them up front is smart. One question: is there a batch queue for converting a folder of files in one go?

The before-and-after reports include units and axes. Could the export screen flag when the source format does not encode units and require an explicit choice before converting to STL? That would help prevent a millimetres-versus-metres mistake when handing a model to a 3D-printing workflow.