Novus Convert
Convert files
Vector & CAD format

X3D converter

An .x3d file is the XML successor to VRML: the same scene-graph concepts — shapes, transforms, viewpoints, interpolators — expressed as XML elements instead of curly braces, standardised so that a document can be validated rather than merely parsed.

Private for supported formats — processed in your browser

Convert supported files

Runs on your device

Drop X3D files here

Batch files can each use a different output. Nothing uploads for local conversions.

Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.

Where X3D comes from

The Web3D Consortium published X3D in 2001 as VRML's reformulation, and ISO standardised it as ISO/IEC 19775. It added profiles (Interchange, Interactive, Immersive, Full) so a reader could declare how much of the language it supported, plus later additions for CAD geometry, volume rendering and physically based materials. X3D is still actively maintained and is the archival 3D format of choice for several museums and standards bodies, even though glTF won the delivery market.

How X3D works

  • XML, so documents can be schema-validated, transformed with XSLT and queried with XPath.
  • Geometry is typically an IndexedFaceSet with a coordIndex attribute using -1 face terminators, or an IndexedTriangleSet with a flat index list.
  • Profiles declare a conformance subset, so a file states up front how much of the language a reader must implement.
  • Coordinates live in a Coordinate node's point attribute as a flat whitespace-separated list of triples.
  • The format also has a compressed binary encoding and a JSON encoding, though the XML form is by far the most common.

When to use X3D

  • Archival 3D storage where a validatable, non-proprietary format is a requirement
  • Scientific and medical visualisation, where the volume-rendering components are used
  • Publishing interactive 3D content that must remain readable decades later
  • Extracting geometry from an X3D archive for use in a modern engine

Strengths and limitations

Strengths

  • A real ISO standard with schema validation, which very few 3D formats offer
  • Text-based and archival, so files remain readable without the authoring tool
  • Profiles make partial support explicit rather than a matter of guesswork

Limitations

  • Verbose even by XML standards, and slow to parse at scale
  • Adoption outside archival and scientific niches is thin
  • Rendering support depends on toolkits rather than being built into browsers

Compatibility

Blender, MeshLab, ParaView, FreeCAD, Xj3D and view3dscene handle X3D; X3DOM renders it in a browser via JavaScript, but nothing renders it natively. Novus Convert reads inline Coordinate points with IndexedFaceSet or IndexedTriangleSet indices locally, and converts to STL, OBJ, 3MF, GLB, glTF, PLY and USDZ. Documents containing a DOCTYPE or entity declaration are refused outright rather than parsed, because external entity expansion is an attack surface with no legitimate use here.

head/meta elements are read as document metadata; the geometry targets have nowhere to put them.

Convert X3D to another format