NFF to PLY Converter
FileFlip converts NFF to PLY 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 NFF file to PLY?#
- Drop your NFF 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 PLY 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 PLY file. Your browser writes it straight to your downloads folder, because there was never a server holding it.
Does converting NFF to PLY lose quality?#
Not in the sense of pixels or samples. Converting NFF to PLY rebuilds the file in PLY's own model rather than re-encoding it, so everything PLY 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 NFF files online?#
Yes, because nothing is uploaded. FileFlip converts NFF 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 NFF to PLY actually does to the file#
Converting NFF to PLY 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, and drops skeleton and animation.
| Engine | Assimp |
|---|---|
| Conversion path | One step: NFF → PLY |
| 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 |
| 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 | Dropped | The target format has nowhere to put it. |
Worth knowing before you start:
- if the source carries a skeleton or animation, this target has no place to store it
What is an NFF file?#
An NFF file is plain text written to Eric Haines' Neutral File Format, first drafted on October 3, 1988 as part of the Standard Procedural Databases project, listing a viewpoint, lights, a background colour and a handful of primitives like spheres, cones and polygons with one letter code starting each line.
Use NFF only when working with an existing ray-tracing benchmark scene or legacy renderer that already expects the format.
Convert NFF to OBJ when its primitives need to become a mesh that a modern 3D application can open.
What is a PLY file?#
A PLY file stores a point cloud or mesh as a list of elements, typically vertices and faces, each carrying whatever properties its writer chose to attach, such as colour, normals or scan confidence, which is why 3D scanners and photogrammetry tools favour it over formats with a fixed vertex layout.
Use PLY straight out of a 3D scanner or photogrammetry tool, since it's built to carry exactly the per-point data those pipelines produce.
Convert PLY to OBJ or glTF once the scan needs to go into a rendering or animation pipeline that expects UV-mapped textures instead of vertex colour.
NFF to PLY questions people ask#
What is an NFF file?
An NFF file is a plain-text scene description in Eric Haines' Neutral File Format, listing a camera, lights, a background colour and simple primitives like spheres, cones and polygons. Haines created it in 1988 as part of the Standard Procedural Databases project, a set of test scenes meant to let different ray tracers be compared on identical input.
What software can open NFF files?
NFF has no mainstream viewer today; support is limited to older ray tracers and a handful of 3D libraries, such as Assimp, that kept a reader for benchmark and archival purposes. A general-purpose 3D application is unlikely to open one directly.
Does NFF support textures or materials?
No, an NFF surface is described with only a fill colour, a diffuse and specular coefficient, shininess, transmittance and index of refraction, with no texture mapping at all. That simplicity is what made it easy for different renderers to implement consistently.
What is a PLY file used for?
A PLY file stores a point cloud or mesh, most commonly the raw output of a 3D scanner or photogrammetry tool, because it can carry arbitrary per-vertex data like colour, normals and scan confidence alongside position. It came out of Stanford's graphics lab in the mid-1990s for exactly that purpose.