Questions

Four tools for 3D files, all of which run in your browser. Convert handles the everyday pairings (FBX to OBJ, OBJ to STL, anything to GLB) and the awkward formats that turn up when a colleague or a supplier sends you something your software refuses to open. Compress makes a model small enough to ship. Render turns it into an image. View lets you look inside it. There is nothing to install and nothing to buy.

Yes. A .max file is an OLE2 compound document holding a class directory and a scene graph of nested binary chunks, and we read that structure directly: no Autodesk licence, no plug-in, no WebAssembly wrapper around somebody else’s C library. Editable Poly and Editable Mesh geometry, UV channels, node transforms and Standard, Physical, VRay, Corona and Multi/Sub-Object materials all come through. What does not is anything 3ds Max computes rather than stores: unfinished modifier stacks, NURBS, particles and procedural geometry live in the application, not in the file.

No. Your model never leaves your computer. Everything happens inside your browser tab using WebAssembly and JavaScript, so there is no upload step and no copy of your file on any server, not a temporary one, not a cached one. We could not look at your model if we wanted to.

Two ways, both of which take under a minute. Open a converter page, disconnect from the internet, and convert a model. It still works, because everything it needs is already on your machine. Or leave the network on, open your browser’s developer tools, switch to the Network tab, and drop a file in: you will see no request carrying your model. Do not take our word for it; the whole point is that the claim is checkable.

Usually well under a second. A dense scan or a scene with millions of triangles can take a few seconds, and that time is spent on your own processor rather than waiting in a queue behind other people’s jobs. There is no upload or download time either, which is where most of the wait goes on server-based converters.

No limit is imposed by us, because there is no server to protect. The real constraint is your browser’s memory: a tab can generally work with models up to a few hundred megabytes. If a very large file fails, closing other tabs usually fixes it.

Because it costs almost nothing to run. The conversion happens on your hardware, so all we are serving is a static page; there are no conversion servers, no storage bills and no queue to scale. That removes the usual reason to charge, gate or advertise.

No. There is no sign-up, no email wall and no per-day quota to reset.

Most likely one of two things. Either the target format cannot store textures at all (STL and PLY are geometry-only by design), or the model references image files that were not included. Formats like OBJ and glTF keep their materials and textures in separate sidecar files, so drag the model, its .mtl or .bin, and the image files into the drop zone together and they will be wired back up.

Only some formats can carry it. FBX, glTF, GLB, COLLADA and USDZ store animation; OBJ, STL and PLY have no concept of it. If you are converting a rigged character, GLB is almost always the right destination.

Formats drift. FBX in particular is proprietary and versioned, and two exporters can produce files that disagree about what FBX means. If a file fails, try re-exporting it from the source application as binary FBX 2013 or later, or as glTF if that is an option. Corrupt or truncated downloads are the other common cause.

75 formats can be read and 19 can be written. The formats reference lists every one of them, what each can store, and where you are likely to run into it.