f3d.app

What is F3D?

F3D is a free, open-source, cross-platform desktop application for viewing 3D data. It is built around a deliberately minimal interface: rather than a full modeling or editing suite, it aims to open a file and show it correctly with as little setup as possible. The project was originally created by Kitware SAS and relies on established open-source libraries such as VTK, OCCT, Assimp, Alembic, Draco, OpenUSD, OpenVDB, PDAL, and OSPRay.

H3 What it can display The feature set points to a viewer that covers more than hobbyist mesh files:

• Realistic rendering — lighting and materials for previewing models as they are meant to look.
• Animations — playback of animated assets, with GPU-accelerated skinning for character rigs.
• CAD — inspection of engineering models and designs.
• Gaussian splatting — visualization of real-world scans captured in that format.
• Volume rendering — volumetric datasets such as medical scans and scientific simulations.
• Scientific visualization — coloring data for accurate scientific views.

H3 Who it suits The natural audience is someone who receives 3D files and needs to check them quickly: an engineer reviewing a CAD part, a researcher inspecting a simulation or scan, an artist previewing an asset with materials and animation, or a developer who wants a lightweight viewer bundled into a workflow. It is less suited to someone who needs to edit geometry, rig characters, or author scenes, since the stated focus is visualization rather than creation.

H3 Practical notes Because it is cross-platform and open source, it can be installed on mixed Windows, macOS, and Linux teams without licensing friction. The trade-off of a minimalist viewer is that convenience comes before depth: expect fast opening and clean rendering, not a deep tool palette. If you want to compare it with other free viewers, Blender is a full creation suite rather than a viewer, while MeshLab leans toward mesh processing and inspection.

A useful next step: download F3D and open one file from each category you actually work with — a CAD export, an animated rig, and a scan or volume — to see whether its default rendering matches how you need to inspect that data.

How do I install F3D on Windows, macOS, or Linux?

F3D is distributed as a desktop application for Windows, macOS, and Linux, and the usual route is to download a ready-to-run package from the official site rather than build it yourself. Start at F3D and look for its download or installation section; that page is the authoritative place for current platform packages.

A practical order of operations:

1. Open the official site and find the download area for your operating system.
2. Pick the package type that matches how you normally install software on that platform.
3. Install it the way that package type expects, then launch F3D and open a sample 3D file to confirm rendering works.

Platform notes:

• Windows: Expect an installer or a portable archive. If you use a package manager such as winget or Chocolatey, check whether F3D is available there before downloading manually.
• macOS: A disk image or archive is typical. Because macOS restricts unsigned or unnotarized apps, you may need to allow the app in System Settings after the first launch attempt.
• Linux: Distributions vary. A Flatpak or AppImage avoids dependency conflicts, while a native package from your distribution's repository is easier to keep updated.

If you prefer building from source, F3D's dependencies are substantial — VTK, OCCT, Assimp, Alembic, and others are named in its acknowledgements — so reserve that route for cases where no prebuilt package fits your system. For most users evaluating F3D as a quick model or scan viewer, the packaged download is the faster path.

Can F3D open and render CAD files such as STEP or IGES?

Yes. F3D is built to open and render CAD files, including STEP and IGES, and its page explicitly lists CAD as a supported use case: "Render CAD designs, allowing you to view and inspect engineering models." That support comes from its integration with OCCT (Open CASCADE Technology), the open-source kernel that handles STEP, IGES and related CAD formats, so CAD import is a first-class capability rather than a side effect of a generic mesh loader.

What that means in practice

• Inspection, not editing. Expect to open a part or assembly, orbit around it, check geometry and take a visual pass over an engineering model. F3D is a viewer, so it is not the tool for modifying solids, adding features or exporting a revised STEP file.
• Assembly structure and materials. CAD files often carry part hierarchies and colour or material assignments. A viewer that reads them through a CAD kernel can typically show those, which is what makes it useful for a quick design review rather than just a shape check.
• Mixed workloads. The same application also handles animations with GPU-accelerated skinning, realistic rendering with lighting and materials, Gaussian splatting, volume rendering for medical or simulation data, and scientific colour mapping. If your work moves between CAD models and scan or simulation data, one viewer covers both.

A quick comparison

How to decide

If your task is "someone sent me a STEP file and I need to see it now," F3D is a reasonable default, especially since it is free, open source and cross-platform, so Windows, macOS and Linux colleagues can all open the same file. If your task is "I need to change this model," keep a CAD authoring tool alongside it.

A useful next step: take one representative STEP assembly from your own work, open it in F3D, and check three things — whether the part tree appears, whether colours and materials survive, and how it feels to navigate a large model. Those three checks tell you more than any feature list. For related viewing needs, Kitware is the organisation behind F3D's origins, and the underlying open-source projects such as VTK and OCCT are worth knowing if you later need to script or extend the workflow.

Does F3D support playing animations in glTF or FBX models?

Yes. F3D lists animation playback as a core capability, with GPU-accelerated skinning for smooth playback of complex character rigs. Since glTF and FBX are both common formats for rigged, animated assets, this is the feature you'd rely on for either.

What this means in practice

• Skinned character rigs (bones driving a mesh) are the target case, not just simple object motion.
• GPU acceleration matters for long or high-bone-count rigs, where CPU-side skinning would stutter.
• Animation support sits alongside F3D's other modes — CAD inspection, Gaussian splatting, volume rendering, scientific visualization — so you can use one viewer across mixed asset types.

A quick way to check for yourself

Open your animated glTF or FBX in F3D and look for playback controls or an animation/clip selector. If your file contains multiple clips, confirm you can switch between them and that the timeline scrubs without dropping frames. If a specific rig plays but a morph-target or blend-shape animation does not, that's a narrower limitation worth noting separately.

Decision criterion

If your workflow is "quickly preview and sanity-check animated assets without launching a full DCC tool," F3D fits. If you need authoring, retargeting, or export of animation data, it won't replace Blender or Maya — it's a viewer.

For format-specific caveats, the project's own documentation is the reliable place to confirm which animation features each importer exposes.

How does F3D handle volume rendering for medical scans or scientific simulations?

F3D includes volume rendering as one of its supported visualization modes, aimed at datasets like medical scans and scientific simulations. According to the project's own description, it performs "advanced volume rendering" so you can visualize complex volumetric datasets, and it also supports coloring data to produce accurate scientific visualizations.

What that means in practice: instead of only showing surface meshes, F3D can display the interior structure of a 3D scalar field — for example, density values from a CT or MRI stack, or output from a fluid or climate simulation. Volume rendering typically lets you see through the data and adjust how density or intensity maps to color and opacity, which is how radiologists and researchers distinguish bone, tissue, or flow regions inside a scan.

Where it fits

• Quick inspection: You have a volume file and want to look at it without launching a full analysis suite.
• Cross-platform, lightweight use: It is a free, open-source desktop viewer, so it suits students, engineers, and researchers who need a fast preview rather than a heavy pipeline.
• Mixed data: Because the same application also handles CAD, animations, Gaussian splatting, and scientific visualization, you can review volume data alongside other asset types in one tool.

Trade-offs to weigh

A general-purpose viewer is convenient, but it is not a replacement for dedicated medical imaging or simulation packages. If you need segmentation, registration, quantitative measurement, or clinical reporting, expect to move the data into specialized software after an initial look. Volume rendering is also GPU- and memory-intensive; large scan stacks benefit from a capable graphics card.

A sensible next step: open one representative volume dataset in F3D, check whether the built-in color and opacity controls give you the clarity you need, and keep your existing analysis tool for the deeper work. For related open-source visualization, VTK is the underlying toolkit F3D credits, and Kitware is the organization that originally created F3D.

Is F3D free to use in commercial projects, and what are its licensing terms?

Yes. F3D is free to use, including in commercial projects. The website describes it as free, open source, and cross-platform, and its page_evidence lists no paid tiers or payment platforms. In practice, that means you can install it on work machines, use it to inspect models and datasets during commercial work, and even bundle or modify it, provided you follow the terms of its open-source license.

The practical catch is that "free to use" and "free to redistribute in your own product" are different questions. The page_evidence does not state which specific license F3D is released under, so the exact obligations depend on the license file in the project's source repository. That matters most if you plan to ship F3D inside a commercial application, modify its code, or offer it as part of a paid service.

What this means in practice

• Internal commercial use: Safe in almost any open-source license. A studio, engineering team, or research group can use F3D to view CAD models, animations, volume data, or Gaussian splatting scans without paying.
• Redistribution inside a product: Check the license first. Permissive licenses generally allow this with attribution and notice requirements; copyleft licenses can impose stronger conditions on how you combine and distribute code.
• Modifying the source: Also license-dependent. If you change F3D and distribute the result, you need to know whether those changes must be shared.

A concrete scenario

Suppose a small engineering firm wants a lightweight viewer for clients to open CAD files. Using F3D internally is straightforward. Shipping it as part of a commercial desktop app requires reading the license and possibly the licenses of its dependencies, since the page_evidence credits projects such as VTK, OCCT, Assimp, and OpenUSD, each of which may carry its own terms.

Next step

Open the F3D project on GitHub and read the LICENSE file, plus any third-party notices. If you only need to view files at your desk, no further action is needed. If you plan to redistribute, have someone confirm the license compatibility before you build it into a product.