X3D

An open, ISO-standardized XML-based format for interactive 3D scenes that succeeded VRML, adding shaders, geospatial data, and multiple encodings while remaining backward-compatible with VRML content.

Extension

.x3d

Full name

Extensible 3D Graphics

Introduced

2001 (announced as VRML's successor; ISO/IEC 19775 ratified 2004)

Vendor

Web3D Consortium

What is inside the container

X3D scenes can be encoded in four interchangeable ways — XML (.x3d), Classic VRML-style text (.x3dv), the original VRML97 encoding (.wrl), and JSON — all describing the same underlying scene-graph model of geometry, materials, lighting, animation, and behavior nodes. It is a direct superset of VRML's node model, extended with CAD, GIS/geo-referencing, medical visualization, humanoid animation (H-Anim), and shader support that VRML never had, and its schema is openly published and ratified as an ISO standard rather than owned by any single vendor.

How to open it

Cross-platform, free viewer InstantReality or the open-source X3DOM/X_ITE JavaScript libraries render X3D scenes directly in a web browser

3D modeling software Blender and other 3D tools support X3D import/export via built-in or add-on importers

Scientific/technical visualization X3D is used directly by tools in medical imaging, GIS, and astronomy visualization for interactive, standards-based 3D delivery

DAM/asset pipeline Convert X3D to glTF for broader compatibility with modern web and game-engine viewers, using tools like Assimp, while retaining the X3D for domain-specific (CAD/GIS) metadata it carries that glTF doesn't

For archives

X3D is a solid archival choice among older interactive-3D formats because it is an open ISO standard (ISO/IEC 19775/19776) with a published, stable specification rather than a proprietary schema — a DAM can store X3D scenes with more confidence in long-term readability than a vendor-locked format. For active delivery, however, most DAM pipelines still convert to glTF, which has broader current tool and browser support, keeping X3D as the standards-compliant archival master.

X3D emerged in 2001 as the Web3D Consortium’s answer to VRML’s aging limitations, joining the consortium’s roadmap as an XML encoding and functional superset of VRML rather than a clean break from it — existing VRML content remains valid X3D content through the format’s Classic VRML and VRML97 encodings. The abstract X3D specification was ratified as ISO/IEC 19775 in 2004, with the XML and Classic VRML encodings (ISO/IEC 19776) following in 2005, giving X3D a level of open, standards-body governance that most competing 3D formats of the era lacked.

Where X3D earns a place in DAM workflows is in scientific, medical, GIS, and CAD visualization — fields that adopted its geo-referencing, humanoid-animation, and shader extensions directly, and that still produce X3D as native output. A DAM archiving this kind of content benefits from X3D’s open, ISO-ratified schema for long-term readability, even though day-to-day preview and delivery in most modern pipelines now runs through glTF, which has wider current browser and game-engine support; the two formats coexist in a DAM the way IFC and RVT do — one for openness and archival durability, one for practical, in-the-moment tooling.

Frequently asked

Is X3D backward-compatible with VRML files?

Yes — X3D is a direct superset of VRML's node model and includes a VRML97 (.wrl) encoding, so existing VRML content is valid X3D content and can be read by X3D-compliant tools.

What are the different ways an X3D scene can be encoded?

Four: XML (.x3d), Classic VRML-style text (.x3dv), the original VRML97 text encoding (.wrl), and JSON — all represent the same underlying scene graph, chosen based on the target application or workflow.

Why would a DAM keep X3D instead of converting everything to glTF?

X3D carries domain-specific features glTF doesn't — geospatial referencing, humanoid animation (H-Anim), CAD and medical-visualization extensions — and it's an open ISO standard, so scientific/GIS/CAD content is often kept in X3D for both fidelity and archival durability.

Can X3D content be viewed directly in a web browser?

Yes, via JavaScript libraries such as X3DOM or X_ITE that render X3D scenes in-browser without a plugin, unlike VRML which required now-discontinued browser plugins.

Is X3D controlled by a single vendor?

No — it is developed and maintained by the Web3D Consortium and ratified as an ISO standard (ISO/IEC 19775/19776), which is a key reason it's considered a safer long-term archival format than proprietary alternatives.

What kinds of assets in a DAM are likely to be X3D files?

Scientific and medical visualization exports, GIS/geospatial 3D models, CAD interchange for humanoid or geo-referenced content, and legacy VRML content upgraded to the X3D container.

How does X3D handle 3D printing or scanning use cases mentioned by the Web3D Consortium?

The Web3D Consortium lists 3D printing and scanning among X3D's supported use areas alongside CAD, GIS, AR/VR, and medicine, though PLY and glTF are more commonly seen in DAM pipelines specifically for scan output.

When did X3D become an official ISO standard?

The abstract X3D specification (ISO/IEC 19775) was first approved by ISO in 2004, with the XML and Classic VRML encodings (ISO/IEC 19776) following in 2005.

Sources

X3D became the successor to VRML in 2001, joining the Web3D Consortium as an XML encoding and superset of VRML. checked 2026-08-07 — Web3D Consortium — X3D & VRML
The abstract X3D specification (ISO/IEC 19775) was first approved by ISO in 2004, and the XML/Classic VRML encodings (ISO/IEC 19776) were approved in 2005. checked 2026-08-07 — Wikipedia — X3D