F3D

F3D is a free, open-source viewer for 3D models, CAD files, and scientific data. It suits designers, engineers, researchers, and developers who want one application across desktop, Android, and the browser. Its format range and visualization depth are impressive, but GPU requirements and importer-specific material gaps make it a better technical workhorse than a universally faithful interchange viewer.

Overview

F3D combines model browsing with high-quality rendering and technical visualization. Realistic lighting and materials can make design reviews and presentation images more informative than a geometry-only viewer. Animation playback and GPU-accelerated skinning extend it to character-rig inspection, while CAD viewing, Gaussian splatting, volume rendering, and scientific visualization cover specialist workflows.

The broad scope has boundaries. FBX PBR materials are unsupported, Alembic files do not support materials, and Gaussian splatting requires OpenGL 4.3, which macOS does not support. F3D is therefore strongest when broad file access and cross-platform availability matter more than identical material fidelity in every format.

Key features

• Rendering: Lighting and material support enables realistic views for model assessment and communication, provided the source format carries compatible material data.
• Animation: Animation support with GPU-accelerated skinning helps inspect articulated characters and rig movement rather than merely viewing a static mesh.
• Technical visualization: CAD, scientific datasets, volume rendering, and Gaussian splatting make F3D relevant to engineering and research as well as general 3D browsing.
• Format coverage: Supported files span VTK and VTK XML, EXODUS II, NetCDF, DICOM, NRRD, MetaImage, TIFF, PNG, JPEG, HDR, OpenEXR, STL, STEP, IGES, BREP, OBJ, glTF, GLB, 3DS, VRML, FBX, COLLADA, DXF, 3MF, USD, VDB, and more. That range reduces the need to maintain separate viewers for common mesh, CAD, imaging, and scientific formats.
• Browser viewer: The web viewer opens or accepts dragged-and-dropped files and exposes rendering and display settings, useful for quick access without installing a desktop package.
• Developer integrations: A Python package, beta JavaScript/WebAssembly package, and libf3d C++ library with Python and Java bindings provide routes for embedding viewing into software. Available plugins can differ by package because F3D relies on libraries such as VTK, Open CASCADE, Assimp, Alembic, Draco, OpenUSD, OpenVDB, PDAL, and OSPRay.

Pricing

F3D costs free on the F3D plan. It is free and open source under the BSD 3-Clause License, which permits redistribution and use in source and binary form, with or without modification, subject to the license conditions. There is no trial period because the software is already free, and there are no paid tiers, seat counts, usage quotas, or renewal charges to weigh.

This makes the same plan suitable for an individual viewer, a classroom, a technical team, or a developer embedding F3D. The trade-off is that there is no paid support or tier designed to remove the technical constraints of particular importers and graphics hardware.

Platforms

F3D provides packages for Windows, macOS, and Linux, plus Android builds for ARM and x86 architectures. A browser-based viewer covers machines where installation is inconvenient. The macOS binary is unsigned; macOS may block it until its quarantine attribute is removed using the documented command. Windows may show a security warning because the portable binary is not yet signed by Microsoft.

Volume rendering and HDRI support require a decent GPU. Gaussian splatting requires OpenGL 4.3, a requirement macOS does not support, so that workflow is not a practical macOS option.

Who it's for

Choose F3D for cross-platform inspection of mixed 3D, CAD, medical-imaging, and scientific files, or for developers who need embeddable viewing components. It is particularly appealing where an open license and broad format coverage matter. Look elsewhere if your workflow depends on FBX PBR or Alembic materials, Gaussian splatting on macOS, or dependable performance on weak graphics hardware.

Pros and cons

• Pros: Free BSD-licensed distribution; unusually broad technical and artistic format support; desktop, Android, and web access; realistic rendering, animation, and specialized visualization; language bindings and a C++ library for integration.
• Cons: Volume rendering and HDRI need a decent GPU; Gaussian splatting excludes macOS; FBX PBR and Alembic materials are unsupported; unsigned Windows and macOS packages can trigger security friction; plugins vary between packages.

Alternatives

For a broad directory of choices, see 3D Model Viewer Software.

Aspose.3D Viewer is a free option across Android, iOS, Linux, macOS, web, and Windows. Pick it when iOS support is essential.

Sketchfab suits hosted model sharing and adds a Basic free tier with a 50MB maximum file size per model; its Pro plan costs $15 a month when billed yearly.

Graphisoft BIMx is a free app and browser viewer for Graphisoft projects, with an account required on iOS, Android, and desktop.

BIMx Web Viewer is the browser-first choice for viewing BIMx files; Pro Model Transfer features require eligible company membership and Graphisoft ID sign-in.

Marmoset Viewer is a free viewer included with Toolbag versions 2.07 and newer.

Dalux fits project and field coordination, with a free Field Basic tier allowing unlimited tasks across up to three active projects or buildings.

Nanome targets collaborative workspaces; its free web seat includes three workspaces, one project, 50 MARA credits, five recent files, and seven days of chat history.

OmniView 3D is a browser-oriented freemium option whose free Starter tier allows three models, 100 MB storage, selected formats, three-day auto-deletion, and a watermark.

Verdict

F3D is the right choice for technically minded users who need a capable, open viewer across many file types and platforms without a license bill. Its main reason to choose it is the combination of specialist visualization and developer integration; its main reason to look elsewhere is format fidelity or hardware constraints, especially on macOS and in material-heavy pipelines.