NDO to glTF Converter
FileFlip converts NDO to glTF entirely inside your browser, using Assimp compiled to WebAssembly. The file is never uploaded to a server: it is read off your disk, converted on your own machine, and saved back by the browser. That means no file-size limit, no queue and no account.
How do I convert an NDO file to glTF?#
- Drop your NDO file onto the converter at the top of this page, or click it to pick one from your computer. You can add as many as you like.
- Leave the target set to glTF and the conversion starts on its own. FileFlip downloads 11.2 MB of WebAssembly the first time and nothing after that, then runs Assimp on your own machine.
- Save the glTF file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting NDO to glTF lose quality?#
Not in the sense of pixels or samples. Converting NDO to glTF rebuilds the file in glTF's own model rather than re-encoding it, so everything glTF can represent comes through exactly and anything it cannot has to be dropped. Expect the geometry to be exact, and anything the target has no place for, such as a rig, to be left behind.
Is it safe to convert NDO files online?#
Yes, because nothing is uploaded. FileFlip converts NDO files inside the browser tab you already have open, using WebAssembly builds of the same engines a desktop converter would install. Your file is read from your own disk into the page's memory, and no request carrying it is ever made.
You do not have to take that on trust. Open your browser's network panel, run a conversion, and you will see the engine come down and your file go nowhere. There is no upload, no server-side copy, no retention window, and no account tied to what you converted.
How FileFlip works lists every engine, its version and its download size, and shows how to check for yourself that nothing leaves your machine.
What NDO to glTF actually does to the file#
Converting NDO to glTF runs on Assimp, downloads 11.2 MB of WebAssembly the first time and nothing after that, rebuilds the file in the target's own model.
| Engine | Assimp |
|---|---|
| Conversion path | One step: NDO → glTF |
| Downloaded to your browser | 11.2 MB, once, then cached by your browser |
| Quality | Rebuilt in the target's model |
| You get back | One file, or a ZIP when the source carries separate materials or buffers |
| Where it runs | In a background worker, so the page stays responsive |
What survives the conversion
| What is in the file | This conversion | Why |
|---|---|---|
| Materials | Sometimes | Survives for some files and not others. |
| Textures | Sometimes | Survives for some files and not others. |
| Skeleton and animation | Sometimes | Survives for some files and not others. |
Worth knowing before you start:
- the result is a single file when the model has no external materials or buffers, and a ZIP when it does
What is an NDO file?#
An NDO file is Nendo's native mesh format, a binary file identified by a "nendo" header that stores an object's edge, face and vertex tables along with UV and texture data for Izware's subdivision modeller.
There's little reason to author new NDO files today; it matters only for opening a model saved by a copy of Nendo.
Convert NDO to OBJ or FBX to bring an old Nendo model into a modeller that's still maintained.
What is a glTF file?#
A glTF file is a JSON scene description, developed by the Khronos Group and first released in 2015, that lists a model's meshes, PBR materials, animations and scene hierarchy while its binary geometry and textures sit alongside it in separate buffer and image files.
Use glTF's JSON form when a pipeline needs to inspect or hand-edit the scene structure directly, since it's plain, indexed JSON.
Convert glTF to GLB when the model needs to travel or load as a single file instead of a folder of JSON, buffers and textures.
NDO to glTF questions people ask#
What is an NDO file?
An NDO file is a Nendo model: an object's edges, faces, vertices and UV data stored in a binary file that starts with a "nendo" header. Nendo was a subdivision modeller from Izware known for a distinctive, box-free workflow built around edge and face selection.
Is Nendo still available to open NDO files?
No. Nendo's publisher, Izware, is no longer active, and there's no current source for the software, which means an NDO file today can only realistically be opened through a library like Assimp that includes a reverse-engineered NDO importer.
Is NDO related to Wings 3D?
Only by inspiration, not compatibility. Wings 3D, the open-source polygon modeller, describes itself as inspired by Nendo and Mirai, two earlier Izware applications, but Wings 3D does not read the NDO format itself.
What's the difference between glTF and GLB?
glTF is a JSON text file that references its geometry buffers and textures as separate files, while GLB packs that same JSON, the buffers and the textures into a single binary file. Both describe the identical data model; GLB just bundles everything one file needs to travel as one upload.