ExPlora4D

3D for the humanities · IIIF-native

Read a 3D model the way you read a source.

ExPlora4D is a web viewer for cultural heritage in 3D. Inspect the surface, annotate what you see, say how certain each part of a reconstruction is, and publish it all as an open IIIF manifest.

  • 30+ 3D formats
  • IIIF Presentation 4
  • EN · PL · DE
  • Web, Drupal, Android, iOS
The wooden synagogue of Wołpa as a textured 3D model The same model in untextured clay with ambient occlusion The same model under a low raking light
The same model under a raking light from the right The same model in its published lighting Published Raking light
The same model coloured by height with contour lines The same model showing its surface normals as colours The same model coloured by level of certainty, with lettered badges The same model cut lengthwise by a section plane, showing the interior The same model with numbered annotation markers The same model in warm evening light The same model in a bounding box labelled with its size in metres The same model as a wire mesh The same model at night under spotlights The same model on its 4D timeline: the weathering of the exterior from 1730 to 1936 The same model on its 4D timeline: the weathering of the exterior from 1730 to 1936 The same model on its 4D timeline: the weathering of the exterior from 1730 to 1936 The same model on its 4D timeline: the weathering of the exterior from 1730 to 1936 The same model on its 4D timeline: the weathering of the exterior from 1730 to 1936 The same model on its 4D timeline: the weathering of the exterior from 1730 to 1936 The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model on midsummer day at Wołpa, lit by the sun from dawn to dusk The same model in the suggested scene: as opened, applied for a presentation and for documentation The same model in the suggested scene: as opened, applied for a presentation and for documentation The same model in the suggested scene: as opened, applied for a presentation and for documentation The same model on each of the viewer's grounds: contact shadow, mirror, grid, turntable, spotlight and dot grid The same model on each of the viewer's grounds: contact shadow, mirror, grid, turntable, spotlight and dot grid The same model on each of the viewer's grounds: contact shadow, mirror, grid, turntable, spotlight and dot grid The same model on each of the viewer's grounds: contact shadow, mirror, grid, turntable, spotlight and dot grid The same model on each of the viewer's grounds: contact shadow, mirror, grid, turntable, spotlight and dot grid The same model on each of the viewer's grounds: contact shadow, mirror, grid, turntable, spotlight and dot grid Wołpa synagogue · reconstruction

The model as it was published: photographic textures, scene lights and environment.shadingMode: "original"

Where the name comes from

Explore + Experience = ExPlora

The name joins two words that begin the same way. Explore is the researcher's side: searching a model, measuring it, questioning it. Experience is the visitor's side: walking round a building that no longer stands, or seeing an object up close. ExPlora4D is made for both.

Ex
Shared by both words, and drawn as the crossed X in the logo.
Plora
From explore, Latin explorare: to search out, to examine.
4D
The three dimensions of the model, and time, in which heritage changes.

The manifest is the view

A IIIF manifest with the viewer's state on board

Standard IIIF carries the scene. The AIM3DViewer block carries what a researcher set up on top of it. Viewers that don't know the block still show the model; ExPlora4D restores the whole reading.

  1. Export from the toolbar after setting up the view.
  2. Validate against the published schema; the viewer checks it on import too.
  3. Share the file or its URL. Opening it restores cameras, lights, shading, annotations and measurements.
  4. Reuse the look on another model: the viewer keeps the lights, rendering and shading and swaps only the model.
// wolpa-synagogue-aim3d-local-night-tour.json
// (excerpt; certainty, timeline and thumbnails as in
// the other examples, measurements as in …-measured.json)
{
  "@context": "http://iiif.io/api/presentation/4/…",
  "type": "Manifest",
  "label": { "en": ["Wolpa Synagogue - night tour"] },
  "items": [{
    "type": "Scene",
    "spatialScale": { "quantityValue": 0.01, "unit": "m" },
    "items": [{ "type": "AnnotationPage", "items": [{
      "motivation": ["painting"],
      "body": {
        "id": "./examples/WolpaSynagogue.glb",
        "type": "Model"
      }
    }] }],
    "annotations": [{ "type": "AnnotationPage", "items": [{
      "motivation": ["commenting"],
      "label": {
        "en": ["Tiered roof"],
        "pl": ["Wielopoziomowy dach"]
      },
      "body": { "type": "Choice", "items": [ … ] },
      "AIM3DViewer": {
        "faceNumbers": [ … ],
        "view": { "position": [ … ], "target": [ … ] }
      }
    }, … ] }]
  }],
  "AIM3DViewer": {
    "camera": {
      "position": [3235, 2380, 3834],
      "target": [-48, 738, -106],
      "fov": 45,
      "aspect": 1.78, "orientation": "landscape"
    },
    "viewer": {
      "theme": "dark",
      "environmentMap": {
        "preset": "studio", "intensity": 0.6, "enabled": true
      },
      "rendering": {
        "toneMapping": "reinhard",
        "exposure": 1.6,
        "postprocessing": {
          "enabled": true, "antialias": "smaa", "ao": true
        }
      },
      "clipping": {
        "mode": { "x": true, "y": false, "z": false },
        "constants": [120, 0, 0]
      },
      "tour": { "autoplay": true, "stepDuration": 8 }
    },
    "lights": [{
      "type": "SpotLight",
      "position": [2500, 300, 2500],
      "color": "#ffc27a",
      "intensity": 4, "angle": 0.45, "penumbra": 0.6
    }, … ],
    "rakingLight": {
      "enabled": true, "direction": 150,
      "height": 10, "sweep": true
    },
    "modelTransform": {
      "shadingMode": "custom",
      "customShader": { "fragmentShader": "…" }
    },
    "measurements": [
      { "mode": "distance", "points": [[0, 0, 100], [0, 1667, 100]] },
      { "mode": "angle", "points": [ … ] }, …
    ],
    "certainty": { "levels": [{
      "value": 10, "code": "A", "symbol": "✓",
      "color": "#1a9850", "label": { "en": ["Surveyed"] }
    }, … ] },
    "timeline": {
      "startYear": 1730, "endYear": 1936,
      "playback": { "loop": true, "speed": 0.5 },
      "stages": [{
        "year": 1781, "type": "documented",
        "nodes": ["Stage_1781"]
      }, … ]
    },
    "thumbnails": [{
      "src": "./examples/gallery/…_side0.png",
      "label": { "en": ["Front"] }
    }, … ]
  }
}

Four things a researcher does with a 3D model

Each tool stores its state in the manifest, under the key shown beneath it. What you set up on screen is what the next reader opens.

Inspect

See the surface, not the texture.

  • Scan viewsOriginal materials, clay, matcap, normals, toon or your own GLSL, with ambient occlusion.modelTransform.shadingMode · postprocessing.ao
  • Raking lightA grazing light that follows the view, for inscriptions and tool marks.AIM3DViewer.rakingLight
  • Sections and measurementClipping planes and profiles; distance, angle, area and volume in real units. Section cuts and finished measurements are saved with the model and exported in the manifest, so they reopen where they were left.AIM3DViewer.clipping · measurements
  • Sun and comparisonThe sun of the model's place on any day, and two looks side by side. See Light.AIM3DViewer.sun · compare

Interpret

Say something about a part of the object.

  • AnnotationsClick or drag over faces; on a point cloud, a click annotates the point.W3C Web Annotation
  • Level of CertaintyEach element graded from surveyed fact to hypothesis, and the model coloured by it.AIM3DViewer.certainty
  • Compare hypothesesAlternative reconstructions or two years of the timeline, swiped or side by side.AIM3DViewer.variants · compare
  • Historical photosOld photographs laid over the model from where they were taken, to check it against its sources.AIM3DViewer.photos
  • Guided toursAnnotations as steps with saved views, played in order.viewer.tour

Publish

Hand the view on, intact.

  • IIIF manifestsExport and import IIIF Presentation 4 with the AIM3D block: cameras, lights, rendering, annotations, measurements.IIIF Scene + AIM3DViewer
  • Embed anywhereAn embed configurator writes the snippet; presentation mode hides the editor.viewer.presentationMode
  • Repository integrationA Drupal module for WissKI-based repositories, with metadata shown beside the model.
  • Screenshots and thumbnailsCapture the view, or render gallery thumbnails from nine angles.

Ingest

Bring in what the project already has.

  • ConversionTo glTF with Blender, IfcConvert (BIM) and OpenCASCADE (CAD), compressed with gltfpack, Draco and KTX2; ZIP, RAR and tar unpacked.
  • Point clouds and splatsLAS, LAZ, E57 and Gaussian splats, streamed by level of detail. See Point clouds.
  • VolumesMicroscope, CT and MRI stacks - Leica LIF, TIFF / OME-TIFF / Zeiss LSM, PNG / JPEG / BMP slices, NRRD, NIfTI, MetaImage, MRC, Volume Graphics VGI, Nikon XTEKCT, DICOM - drawn as a volume: maximum intensity, translucent or surface, with channel colours and, for CT, Hounsfield windows.
  • Sound and imagesAudio files - WAV / Broadcast Wave, MP3, FLAC, Ogg, M4A - and 2D images - JPEG, PNG, WebP, AVIF, GIF, BMP, alone or a ZIP of them - with their tags, markers, EXIF and resolution. See Sound and images.
  • BlenderAn add-on imports and exports AIM3D manifests: a scene set up in Blender opens in the viewer as it was.

Point clouds, from a quick look to a whole site

Laser scans and photogrammetric point clouds open in the browser as they are, or stream from an octree so that only the points the view needs are downloaded. Colour, size and lighting are worked out on the graphics card, and the tools work on the points themselves.

  1. A laser scan of a house as a point cloud, its edges shaded by Eye-Dome Lighting

    Eye-Dome Lighting

    Each point is shaded by the depth of its neighbours, so edges and creases read without normals. A LAZ scan in UTM coordinates, opened directly.

    viewer.pointCloud.edlStrength
  2. The same scan coloured by height, from blue to red

    By height, intensity or class

    Colours are switched in the shader, never rewritten point by point. The adaptive point size follows the density of the scan and keeps surfaces closed at any distance.

    viewer.pointCloud.colorMode · sizeMode
  3. The point cloud of the Wołpa synagogue, streamed and coloured by height

    Streamed level of detail

    The Wołpa synagogue as a streamed point cloud: the coarse levels arrive first, finer nodes load as you come closer.

    Potree 2 · 3D Tiles
  4. A profile through the house: walls, ceilings and roof in section

    Profiles

    Two clicks draw a line; a thin vertical slab of points along it stays, seen square from the side. Walls, floors and the roof in section, ready to measure.

    point cloud panel · Profile
  5. The Tempietto as Gaussian splats, streamed from a level-of-detail RAD file

    Gaussian splats, streamed like an octree

    SPZ, SPLAT, KSPLAT, SOG or a PLY of splats, drawn with Spark. The server builds a level-of-detail RAD file once; the viewer fetches it in chunks, the coarse levels first, and only what is in view takes graphics memory.

    SPZ · SPLAT · KSPLAT · SOG → RAD (build-lod)
The Tempietto as Gaussian splats, streamed from a level-of-detail RAD file

Gaussian splats, streamed like an octree

3D Gaussian Splatting captures (SPZ, SPLAT, KSPLAT, SOG or a PLY of splats) sit next to meshes and point clouds, drawn with Spark. On upload the server builds their level-of-detail tree once, as a RAD file. The viewer reads its header and then fetches the tree in chunks of 64,000 splats by range requests: the coarse levels first, finer ones where you look. The capture shows after a few hundred kilobytes and sharpens as you look around, and only what is in view takes graphics memory.

SPZ · SPLAT · KSPLAT · SOG → RAD (build-lod)

Splats in the scene's light

Captures already hold the light they were taken in: the viewer does not replace their colours but scales them by the scene's lights. Normals, shadows and occlusion come from a volume of the surface built on upload (SPLAT, SPZ, 3DGS PLY).

  1. The Angel as Gaussian splats under three-point studio light

    Studio light

    Three directional lights; a splat's normal is its shortest axis, turned to the camera.

    AIM3DViewer.lights
  2. The Angel splats under a low raking light from the left

    Raking light

    Soft shadows, marched through the voxel volume of the surface towards the light.

    <model>.light
  3. The Angel splats in a low, warm evening sun under a blue sky

    Golden hour

    A low warm sun and a blue sky, whose light the volume darkens in hollows.

    viewer.splatLighting.occlusion
  4. The Angel splats at night, lit from below by a warm floodlight

    Night

    A floodlight from below casts shadows upwards; the exposure brightens splats as it does meshes.

    AIM3DViewer.viewer.splatLighting

From the scanner to the screen

Open directly
LAS and LAZ decoded in a Web Worker while they download, on screen from the first 100,000 points.
Quick preview
Uploads show a shuffled sample of a million points within seconds, before the octree is built.
Octree
PotreeConverter makes a Potree 2 octree of LAS, LAZ, E57 and PLY: three files, every attribute kept.
Delivery
Nodes fetched by HTTP range requests, cached by nginx in 1 MB slices and served by a CDN.
Coordinates
UTM and Gauss–Krüger re-centred in double precision: millimetres kept, the scan upright.

Seeing

  • Adaptive point sizeIn world units, from the estimated spacing of the scan, or fixed in pixels.
  • Square, round or sphereSpheres write their depth, so overlapping points meet as a surface.

Filtering and measuring

  • Class filterA check box per class in the scan: hide the vegetation to measure the building behind it.
  • Picking on the GPUThe ruler and the camera's focus take the point under the cursor, read from a buffer of point ids.

Annotating

  • Point annotationsA click on the cloud annotates that point, stored as a IIIF point annotation; it works on streamed clouds too.

An AI assistant that reads the data with youNew

It explains, translates questions into filters and checks the documentation, always next to the data it came from. It never decides for you: every answer is marked as AI-generated, and the counts and sums are computed from the model itself.

The model check, in plain language

The validation report turns glTF-Validator codes into a verdict and a short list of what matters to viewers and what to fix first: a model in millimetres, textures too big for phones.

File › Validation report

Ask the building model

"Load-bearing walls on level 2", "total slab area": a question about an IFC model becomes a filter you can see, run on every element, then highlighted, isolated or hidden.

Model › Ask the building model

Variants and paradata

Reconstruction variants compared with the viewer's own measurements ("the roof of B is 3.2 m higher"), and each one's sources and Level of Certainty reviewed in the spirit of the London Charter.

Variants › Compare and review paradata

Point clouds, classified on upload

Raw scans get ground, vegetation, buildings and noise before they are streamed, so the class filter works from the first view. On the server, with your own segmentation model if you have one.

Point cloud settings › Classes

Business+ The AI assistant comes with the Business and Enterprise plans, in the web viewer and in the app.

Only what a feature needs goes to the assistant (the validation report, the names of the IFC properties, the variants' texts and measurements), never the model files. A project can switch it off, or run it with its own key and model on its own server.

Time as the fourth dimension

A reconstruction is not one moment. The 4D manifest of the Wołpa synagogue follows its exterior from 1730 to 1936: fifteen stages on a time axis, each with its year, its kind and a description. Any year in between can be chosen; the stages around it fade into each other.

  • Documented event: a date the sources give
  • Modelled stage: weathering placed between the events
  1. The synagogue in 1730: construction
    c. 1730documented

    Construction

    Fresh, light timber and shingles.

    Source: the sources give only “first half of the 18th century” (or the mid-17th century), so the year is conventional.

  2. The synagogue in 1780: old, mossy shingles
    1780modelled

    Old, mossy shingles

    50-year-old shingles, dark, with moss on the northern slopes.

  3. The synagogue in 1781: new shingles
    1781documented

    New shingles

    The roof is light again; the walls stay 50 years old.

  4. The synagogue in 1902: the roof before the repair
    1902modelled

    The roof before the repair

    The 121-year-old roof just before the repair, heavily overgrown with moss.

  5. The synagogue in 1903: roof repair
    1903documented

    Roof repair

    Shown as a complete replacement of the roofing.

    Source: mentions only a repair of the roof.

  6. The synagogue in 1936: final state
    1936modelled

    Final state

    Almost as in the original model (the surveyed state).

What a stage says
Each stage has a year (marked approximate when the sources only give a period), a type, a label and a description, in every language of the manifest. A documented stage can name its source, so the reader sees what the date rests on. nodes name the parts of the model that show the building at that point.
Moving along the axis
With "transition": "interpolate" the two neighbouring stages are faded by the year: 1841 is mostly the 1840 state, 1869 almost the 1870 one. "step" keeps one stage until the next year is reached and fades over transitionDuration seconds. A jump to another year plays as a short time-lapse.
Playback
Play runs through the years at yearsPerSecond (times the chosen speed) and holds on every documented event for pauseAtEvents seconds. The panel's arrows step from stage to stage; the slider picks any year.
// wolpa-synagogue-aim3d-local-4d.json (excerpt)
"AIM3DViewer": {
  "timeline": {
    "startYear": 1730, "endYear": 1936,
    "transition": "interpolate",
    "transitionDuration": 0.8,
    "playback": { "yearsPerSecond": 10, "pauseAtEvents": 1.5 },
    "stages": [
      {
        "year": 1903,
        "type": "documented",
        "label": { "en": ["Roof repair"] },
        "description": { "en": ["Shown as a complete replacement…"] },
        "source": { "en": ["The source mentions only a repair…"] },
        "nodes": ["Stage_1903"]
      },
      { "year": 1912, "type": "modelled", … }
    ]
  }
}

One view, different light

The Wołpa synagogue from the same camera. The sun stands where it stood at the synagogue's place on midsummer day; the other images are raking light, two stages of the timeline set against each other, and the night lights of a manifest.

  1. The synagogue in the morning sun, shadows to the west

    Morning, 8:30

    Low sun from the east, long shadows across the ground.

    AIM3DViewer.sun
  2. The synagogue in the midday sun, short shadows

    Solar noon, 13:20

    The sun high in the south, about 60° up: short shadows close to the walls.

    AIM3DViewer.sun
  3. The synagogue in the evening sun, shadows to the east

    Evening, 19:40

    Low sun from the west, the other side of the building in shade.

    AIM3DViewer.sun
  4. The same view under a low raking light

    Raking light

    A grazing light tied to the view brings out the shingles and the timber joints.

    AIM3DViewer.rakingLight
  5. The synagogue in 1781, with new shingles The synagogue in 1780, with old, mossy shingles 1780 1781

    Comparison

    1780 on the left, 1781 on the right of the swipe divider: the old, mossy shingles against the new ones. Drag the divider.

    AIM3DViewer.compare
  6. The same view at night under spotlights

    Night lights

    The lights a manifest sets: spotlights on the facades, the sky dark.

    AIM3DViewer.lights

Weather around the modelNew

Fog, rain, snow or a thunderstorm around the model, computed on the graphics card and kept in the manifest with the view.

  1. Tempietto in morning mist, lit by a low sun

    Morning mist at sunrise

    Banks of mist on the ground, gilded by the low sun of the sun study.

    AIM3DViewer.weather
  2. The Wołpa synagogue standing in a layer of mist

    Mist

    Its height, density and spread are settings: clumps of low cloud or an even blanket.

    AIM3DViewer.weather
  3. The synagogue's shingle roofs in a downpour

    Downpour

    No rain under the eaves; drops splash and bounce on the roofs, the shingles darken and shine.

    AIM3DViewer.weather
  4. The synagogue in falling snow, its roofs white

    Winter

    Snow settles where the surfaces face up and melts again when it stops.

    AIM3DViewer.weather
  5. Tempietto in a thunderstorm, lightning behind it

    Thunderstorm

    Wind-driven rain, lightning with its flash and, if you want it, the thunder.

    AIM3DViewer.weather

A building is never seen in a studio. The viewer puts it in fog, rain, snow or a thunderstorm, under a sky with clouds and the sun where the sun study puts it.

On the model itself. Rain stops on the model's roofs and splashes there, the surfaces get wet and snow settles on them; mist lies in banks on the ground.

The seasons. The seasons of the intro come along too: petals in spring, pollen in summer, falling leaves in autumn and snow in winter, each with its own colouring of the model.

On the graphics card. Everything is computed on the graphics card, scales with the model, and works in WebGL and WebGPU, in the browser and in the app.

In the manifest. A manifest stores the weather with the view, so a curator can open the synagogue on a misty autumn morning.

Generated surroundingsNew

A typical setting of the period round the model - a village, a town, a stronghold, a shtetl, a monastery, a port, across Europe - drawn from its metadata and marked as generated.

  1. A late medieval village round the synagogue: cottages along the roads, a brick church, fields and a river

    A village, late Middle Ages

    Thatched and shingled cottages along the roads, a brick church, strip fields, a river with willows; the shadows follow the sun.

    AIM3DViewer.surroundings
  2. An early medieval stronghold in winter: timber houses behind a palisade, a frozen moat round the model

    A stronghold about 1150, in winter

    Timber houses behind a palisade, a moat round the castle, snow on the roofs and ice on the water.

    AIM3DViewer.surroundings
  3. A town about 1700: plastered houses, a church tower with a baroque dome, ramparts with bastions

    A town about 1700

    Taller plastered houses, a church tower under a baroque dome, earthen ramparts with bastions instead of walls.

    AIM3DViewer.surroundings
  4. A town about 1890: tenements, a boulevard with trees, a river with bridges, a factory by the railway

    A town about 1890

    Tenements, a boulevard with an avenue where the walls stood, a railway with a factory and its chimney, bridges over the river.

    AIM3DViewer.surroundings
  5. A shtetl about 1780: timber houses gable to the market square round the synagogue, a church with an onion dome behind it, strip fields

    A shtetl about 1780

    Narrow timber houses gable to the market square, a road out of every side, a church off the square, no walls.

    AIM3DViewer.surroundings
  6. A monastery's precinct about 1700: a brick wall with a gate tower, the cloister's ranges, a granary, an orchard and two fishponds

    A monastery's precinct

    A wall with a gate tower, the cloister's ranges beside the church, a granary, an orchard and fishponds; a village farther on.

    AIM3DViewer.surroundings
  7. A Mediterranean town about 1650: rendered houses in lime and ochre under low terracotta roofs, a bell tower, olive groves

    The Mediterranean

    Stone and render in lime and ochre, low terracotta roofs or terraces, a bell tower beside the church, olive groves and cypresses.

    AIM3DViewer.surroundings
  8. A town in 1946: burnt-out, roofless shells among the standing houses, the church and the factories by the railway

    A town in 1946

    Burnt-out, roofless shells among the standing houses; no new blocks yet - the estates come in the late 1950s.

    AIM3DViewer.surroundings
  9. A town about 1975: tenements among blocks of flats inside the boulevard, a housing estate of prefabricated slabs beyond it, factories by the railway

    A town about 1975

    Tenements among new blocks inside the boulevard, a housing estate of prefabricated slabs beyond it, the strips ploughed into wide fields.

    AIM3DViewer.surroundings
  10. A town about 2015: the old town inside its boulevard, renovated blocks, detached houses round the edge, a shop out of town

    A town about 2015

    The estates renovated in pastels, detached houses along the roads round the old edge, a shop with its car park out of town.

    AIM3DViewer.surroundings
  11. A village in the North about 1750: timber houses painted Falu red and ochre under turf roofs, a whitewashed church with a tall spire, spruce woods

    The North

    Timber painted Falu red and ochre under turf roofs, a whitewashed church with a tall spire, spruce and pine all round.

    AIM3DViewer.surroundings
  12. A British town about 1890: rows of red-brick terraces under slate, a stone church with a square tower, a mill by the railway

    The British Isles

    Red-brick terraces under slate, a stone church with a square tower, cottages under thatch and fields in hedgerows outside.

    AIM3DViewer.surroundings
  13. A village in Eastern Europe about 1880: log and whitewashed houses gable to the road under thatch, a church with a green onion dome

    Eastern Europe

    Log houses and whitewashed ones gable to the road under thatch, a church with an onion dome, birch and pine.

    AIM3DViewer.surroundings
  14. The same kind of town drawn plain: pale shapes without textures

    The plain look

    The default: pale shapes without textures, so that nobody takes the setting for part of the model.

    AIM3DViewer.surroundings

A building rarely stood alone. From what the model's metadata say - what it is, its century, its place - the viewer draws a typical setting round it. It is a hypothesis about the kind of place, not a reconstruction of this one, and the viewer says so.

Marked as generated. A badge over the view says what it is; the manifest keeps only its parameters, with generated: true; nothing of it is picked, measured or exported with the model.

The real place. Where the place is known: its terrain from open elevation data, its rivers and lakes from OpenStreetMap - or from OpenHistoricalMap for the year - and the region's brick or stone.

Old maps. An old map can be laid over the ground, and its roads, fields and buildings taken from a digitised file - or read from the map by AI, corrected over the map in the viewer and saved as GeoJSON.

Through time. From 900 to 2025: a year slider whose milestones - 1250, 1550, 1800, 1914, 1945, 1990 - say what changes, and a play button that lets the years go by; or the 4D timeline, the settlement growing house by house.

A scene that stays connectedNew

Change a number in a table, save a file, or turn the model on your phone: the scene follows at once, and nothing is loaded again.

  1. Tempietto with its parts coloured by moisture readings, a table of the readings beside it

    A table drives the model

    Each row is a part of the model. Its numbers give the part a colour, a label and an alert; a changed cell blends in and flashes.

    AIM3DViewer.data
  2. The same model on a screen and on a phone, turned together in a shared session

    One scene on every screen

    Send a link: whoever moves the camera, the year or the section moves them for everyone. A phone is the remote control.

    ?session=…
  3. The scene's settings edited as text beside the model

    A manifest that is followed

    Edit the manifest where it lives, or type its settings beside the model. Only what changed is applied; the camera flies there.

    AIM3DViewer

A viewer usually shows a file as it was when the page opened. This one keeps listening: to a table of measurements, to the manifest, to the model's own file and to the other people looking at the same scene.

Live data. A CSV, a JSON feed or a published spreadsheet is read again every few seconds. Moisture on a wall, the condition of a column, a sensor over its limit: seen on the part it belongs to.

Shared session. A lecture, a meeting or an exhibition: the audience opens the link and sees what the speaker shows, live. Anyone may take the lead.

Followed manifest. Lights, weather, the year, comments: changed in the file, they change on screen, and the model is not loaded again.

Followed model file. Keep the viewer open beside the modelling program. Each save brings the new model in under a cross-fade, with the camera, comments and section kept.

Sound and 2D imagesNew

Not only models: sound files and photographs open in the viewer too, with tools of their own, and sound can be placed in a model's scene.

  1. A soundscape drawn as a landscape of its spectrogram, its waveform in front, the player window beside it

    Sound as a landscape

    An audio file opens like a model: its spectrogram as a terrain, the waveform in front, a playhead moving with the time. Markers, a part in a loop, filter, reverberation.

    WAV · MP3 · FLAC · Ogg · M4A
  2. The Tempietto with the Sounds window: wind everywhere, a bell on the roof, a hum aimed out of the door

    Sound in the scene

    Wind everywhere, a bell from a point, a voice in a cone: heard from where the camera is, placed with a click, tied to years of the 4D timeline.

    AIM3DViewer.sounds · IIIF PointAudio
  3. A guided tour stop on the Tempietto, its narration's caption over the scene

    Narrated tours

    An annotation can tell its story: the tour plays the narration when the camera arrives, shows its captions and goes on when it has been told.

    annotation audio · WebVTT
  4. A section through the Wolpa Synagogue's prayer hall, the Sounds window with its reverberation worked out per octave band

    How the room sounded

    The reverberation of the reconstructed hall, traced through the model's own walls: wood or stone, empty benches or a full house, open windows or a lost roof. The scene's sounds are heard in it.

    sounds.acoustics · Web Worker
  5. A worn inscription: the original left of the line, in relief right of it

    Relief for worn surfaces

    A 2D image is embossed in a light you turn: inscriptions, coins and tool marks read again, against the original on the other side of the line.

    AIM3DViewer.image
  6. Faded ochre figures on rock brought out in strong colours by a decorrelation stretch

    Faded pigments

    A decorrelation stretch, levels, equalisation and false colour on the graphics card; the result saved as PNG. A 300 dpi scan is measured in centimetres.

    dstretch · autoLevels · equalize
  7. Three images of a set side by side in the grid view

    Sets of images

    A ZIP of photos or several images dropped together: a filmstrip, the arrow keys and a grid of all of them, the same settings for each.

    ZIP · JPEG · PNG · WebP

A reconstruction has more sources than a model: recordings, photographs, scans and drawings open in the viewer too, and the manifest keeps them.

Field recordings. A recording opens as a landscape of its spectrogram, with its markers, tags and levels, and plays through a filter, a compressor or the reverberation of a church.

A scene that sounds. The wind, a bell on the roof, a voice from a doorway, heard as the camera moves and changing with the years of the 4D timeline; a guided tour can be narrated, with captions.

The room's acoustics. The sounds are heard as the reconstructed room would have sounded: its reverberation is traced through the model's walls, from what they were made of and what stood on the floor.

Photographs, scans and drawings. Relief, decorrelation stretch, levels, equalisation and false colour bring out what the eye no longer sees, compared with the original, saved as PNG, measured at their real size; a series with a filmstrip and a grid.

In the manifest. The manifest keeps all of it, in IIIF Presentation 4 where it has a word for it.

A scene suggested for the modelNew

The viewer suggests the light, the weather and the rendering from what it knows of the model, for documentation or for a presentation.

The Wołpa synagogue in the late afternoon sun of its place, next to the Suggested scene window: sun, weather, tone mapping and ambient occlusion ticked, each with how sure it is and why
  1. The Wołpa synagogue as opened, in the published lighting

    Wołpa: as opened

    The lighting the model was published with.

  2. The Suggested scene window beside the synagogue: sun, weather, tone mapping and ambient occlusion ticked

    The suggestions

    For a presentation: the place's sun, a clear sky, AgX and AO, each with how sure it is and why.

  3. The synagogue in the late-afternoon sun of Wołpa, under a clear sky

    Presentation

    Wołpa's late-afternoon summer sun, with long shadows.

  4. The synagogue in an even, neutral light for documentation

    Documentation

    An even, neutral light that hides nothing, with AO.

  1. The Tempietto as opened, in the evening sun its manifest sets

    Tempietto: as opened

    Its manifest's summer evening in Rome, in the timeline's year 1520.

  2. The Suggested scene window beside the Tempietto: the sun as it is, weather and tone mapping ticked

    The suggestions

    The sun is already right; the window ticks only the sky and AgX.

  3. The Tempietto in the evening sun of Rome, under a clear sky

    Presentation

    A clear Roman sky with haze towards the horizon.

  4. The Tempietto in a neutral light for documentation

    Documentation

    The sun off, a neutral light for the colours and the stone.

The viewer suggests the sun, the weather, the raking light, the tone mapping and the ambient occlusion from what it knows of the model: its texts, its place and year, its size and its shape. First it settles what the view is for: documentation, in an even light that hides nothing, or a presentation, in the sun of the place and the time. Each suggestion says how sure it is and why. Nothing changes until you apply it, and Undo puts the scene back.

Rules first

Words in the file name, the metadata and the manifest, in English, Polish and German: castle, interior, inscription, winter, fog. The year or century, the size in metres, and what the model is: a scan or splats keep the light they were captured in.

Look › Suggested scene

The place from its name

"Zamek w Malborku" puts the sun over Malbork. The server finds the towns the texts name in GeoNames, offline, with Polish and German endings ("w Krakowie", "pod Łęczycą"). An unsure match is shown as a guess to check.

POST /api/geo/places

A language model in the browser

Where no keyword decides ("nawa główna", "Kreuzgang"), a small multilingual model reads the texts in the browser and says whether they describe an interior, a building outside or an object, and relief to read. It is downloaded once, on your click.

multilingual-e5-small · transformers.js

The shape itself

Rays from inside the model tell walls seen from inside, a room or a nave, from the back of a closed building. A ground without a ceiling means the open air, and a thin plate gets the raking light. It takes a fraction of a second, even for half a million triangles.

orientations · enclosure · proportions

No key is needed, and the model never leaves your device: the rules, the language model and the shape run in the browser. Only the texts go to the server for the place search, to its own GeoNames copy.

How sure are we about this roof?

A reconstruction mixes what survives with what is inferred. ExPlora4D lets every annotation carry a certainty grade, colours the model by it, and keeps the scale in the manifest so others can read it the same way.

LevelCodeBasisScore
✓APreserved / surveyed10
■BDirect documentation8–9
▲CIndirect sources6–7
≈DAnalogy4–5
?EHypothesis0–3

Each level has a colour, a letter and a symbol, so the scale reads without colour vision and in black-and-white print.

A grade applies to one object or to its whole group. The legend counts assessed objects per level; click a level to show only those parts.

Projects can define their own scale, labels and colours in the manifest; the default above is used otherwise.

The synagogue reconstruction coloured by level of certainty
Badges replace annotation numbers with the level's code and symbol while the certainty view is on.

What the model stands onNew

Six grounds under the model, from a barely visible shadow to a turntable with a compass and a scale bar. Each says something different about the model: that it stands, how big it is, where north is, or nothing but the object itself.

  1. The synagogue on a soft contact shadow, with no floor

    Contact shadow

    The default: a soft shadow where the model touches the floor, and no floor. The model stands, without a word about the place.

    ?ground=contact
  2. The synagogue reflected in a glossy floor

    Mirror

    A glossy floor with the model's reflection, fading out round it. For a presentation or an exhibition screen.

    ?ground=mirror
  3. The synagogue on a technical grid fading into the distance

    Grid

    A grid without edges: lines every power of ten below the model's size, finer ones at a tenth, the axes in colour. For size, position and level.

    ?ground=grid
  4. The synagogue on a disc with a compass rose and a 10 m scale bar

    Turntable

    A disc with a compass and a scale bar in the model's unit. For documentation: north and size in one picture.

    ?ground=turntable
  5. The synagogue in a dark room, in a pool of warm light

    Spotlight

    A dark room with a pool of warm light; the background comes back when you choose another. For a single object, as in a museum case.

    ?ground=spotlight
  6. The synagogue on a light dot grid

    Dot grid

    Small dots on paper, fading out: a quiet scale for drawings and prints.

    ?ground=dots

It follows the model. Every ground is built again for each model, from its size.

The Ground window beside the synagogue on the turntable: six tiles, Turntable marked
Look › Ground: a window of tiles that stays open after a pick, to compare. It moves by its header, minimizes to an icon and closes.

Round numbers. The grid's step, the dots' spacing, the disc and the length of the scale bar, rounded to 1, 2 or 5 metres, centimetres or kilometres.

A shadow that keeps up. The contact shadow is drawn again when the model moves, a part is hidden or an animation plays.

Who chooses. A link with ?ground= first, then the manifest (viewer.ground, which the viewer's export also writes), then your pick in the window, then the site's settings. A pick wins over the manifest until the next model, so a curator can open the synagogue on the turntable and you can still try the others.

By mode. The sun study casts its shadows on every ground. Point clouds, splats and streamed 3D Tiles have no surfaces to cast a contact shadow, so they get a soft blob; with the WebGPU renderer the mirror falls back to that blob too and the grid is a plain one. In augmented reality the ground disappears and the model stands on your real floor.

Every model with a name, a type and its rightsNew

A model added to the repository is described in a short form: its name and type, then the author, copyright, licence, date, place and unit. Its owner can change them later.

  1. The form shown when a model is added: name and type required, then date, author, copyright, licence, place, model unit and description

    Described when added

    The form opens before the upload starts. The name starts as the file's, the type is chosen from a list; the rest is optional.

  2. The list of repository models: each with its name, its type as a label and the upload date, with buttons to edit and delete

    Found by name and type

    The model list shows the given name instead of the file name, and the type as a label next to the date.

  3. The Model details window of the Wołpa synagogue: vertices and faces, then name, type, author, copyright, licence, date and place

    Read with the model

    Model details lists them for every model; its owner edits them there or from the list.

The metadata is also what the viewer reasons from. The type says whether a model is a building, an interior or an object on its own; the place and the date put the sun where and when it stood; the unit gives the scale in metres. The suggested scene reads them with the rest of the model's texts, and they are the base for picking the type, scale and lighting on their own.

Required: name and type

Seven types: building, interior, town or settlement, site or landscape, object, sculpture or architectural detail, and other. Enough to tell an outdoor scene from a room or a showcase.

Upload › Describe the model

Rights stated up front

Author, copyright holder and a licence from the Creative Commons list, public domain or all rights reserved, so whoever opens the model knows how it may be used.

CC BY · CC BY-SA · CC0 · …

Only the owner edits

The person who uploaded the model, and the admins, can change its metadata; everyone else reads it. A private model's metadata stays as private as the model.

POST /api/jobs/{id}/metadata

Built on open standards

Nothing about a model or its interpretation is locked inside the viewer. The data stays in formats other tools already read.

StandardMaintained byUsed for
IIIF Presentation API 4IIIF ConsortiumScenes, models, cameras, lights, transforms and comments; import and export of whole manifests.
Web AnnotationW3CComments and assessments on faces and regions, with commenting and assessing motivations, point and WKT selectors.
glTF 2.0Khronos GroupThe delivery format, with Draco and Meshopt geometry compression, KTX2/Basis textures and unlit materials.
3D TilesOGCStreaming large meshes and point clouds at the level of detail the view needs.
Potree 2Potree project, TU WienThe octree format for large point clouds: three files, each node read with a range request, intensity and classification kept.
RADSparkThe level-of-detail format for Gaussian splats: a header and chunks of 64,000 splats, read by range requests as the view needs them.
IFCbuildingSMARTBuilding models, read in the browser or converted with their property sets kept as metadata.
LAS / LAZ, E57ASPRS · ASTMLaser-scan point clouds: LAS 1.0–1.4 in every point format, decoded in the browser, with the ASPRS classes coloured and filtered; converted to Potree 2 or 3D Tiles.
HTTP range requestsIETF (RFC 9110)Reading single nodes of an octree, or chunks of a splat tree, out of one large file; resumable downloads.
JSON Schema 2020-12JSON SchemaThe AIM3D manifest block, published and validated on import.
WissKIWissKI communityDrupal-based, CIDOC CRM–aware repositories that host the models and their metadata.

Technology

A WebGL viewer in the browser, a conversion worker on the server, and the same code packaged for repositories and phones.

In the browser

  • three.js r187
  • WebGL 2
  • GTAO
  • 3d-tiles-renderer
  • Web Workers
  • loaders.gl
  • laz-perf
  • Eye-Dome Lighting
  • GPU picking
  • Volume ray marching
  • Web Audio API
  • Ray-traced acoustics
  • WebVTT
  • geotiff.js
  • web-ifc
  • Draco
  • Meshopt
  • KTX2 / Basis

Logarithmic depth for city-scale and coin-scale models alike; a post-processing chain with SMAA, FXAA and seven tone mappings. Point clouds are decoded off the main thread and coloured, sized, filtered and picked in shaders.

On the server

  • Python worker
  • Blender + Cycles
  • IfcOpenShell
  • OpenCASCADE
  • trimesh
  • PotreeConverter 2
  • py3dtiles
  • laspy + lazrs
  • pye57
  • tifffile
  • pydicom
  • gltfpack
  • PHP
  • Docker

One docker compose up runs the viewer and the full conversion pipeline, with accounts and upload limits. Converted files go out with range requests, gzip and ETags.

Delivery and quality

  • Rollup
  • Drupal module
  • Capacitor
  • Android
  • iOS
  • nginx slice cache
  • Cloudflare
  • Playwright
  • GlitchTip
  • i18n EN · PL · DE

End-to-end tests in a real WebGL browser cover loading, editing, export and the manifest schema.

Follow your file

Every format the viewer reads, grouped. Pick yours: the steps it goes through on the server, what each one makes, and what the viewer shows in the end. Greyed-out steps are skipped.

  1. 1

    Upload

    The file, or a ZIP, RAR or tar archive with its textures and materials, unpacked on the server.

    model.glb
  2. 3

    Checks and compression

    glTF-Validator checks the model (specification, units, size); gltfpack compresses it: Meshopt geometry, KTX2 textures.

    model.glb
  3. 4

    Lighter copies and LoD

    From 2 MB up, a preview GLB (about 10% of the triangles, textures up to 512 px) loads first and the full model replaces it.

    model.preview.glb
  4. 5

    Renders

    Blender Cycles renders thumbnails from nine angles.

    views/*.png
  5. 6

    In the viewer

    A mesh with its materials, in any shading mode, with sections, measurements and annotations.

Directly in the browser: Also opens in the browser as it is: glTF is the viewer's own format.

How each format is handled

FormatIn the browserConverted on uploadAnimation
glTF / GLBNative format–✓
OBJ · PLY · STLthree.jsBlender → GLB–
FBX · DAEthree.jsBlender → GLB✓
IFCweb-ifcIfcConvert → GLB, property sets kept as metadata–
WRL (VRML)three.jsBlender → GLB–
USD · USDA · USDC · USDZthree.jsBlender → GLB (USD-enabled build)–
3MFthree.jstrimesh → GLB–
KMZthree.js–✓
three.js JSONthree.js–✓
3DS · AMF · VOX · XYZ · PCDthree.js––
3D Tiles · Potree 2Streamed level of detail (3d-tiles-renderer); Potree nodes read by range requests––
LAS / LAZWeb Worker: LAS decoded while downloading (point formats 0–10), LAZ with laz-perf; shown from the first points, thinned above a point limitQuick preview, then PotreeConverter → Potree 2 (or py3dtiles → 3D Tiles)–
E57 · PLY (points)–pye57 / trimesh → LAS → Potree 2, with a quick preview–
SPZ · SPLAT · KSPLAT · SOG · PLY (splats)Gaussian splats (Spark), drawn from a level-of-detail tree built while loadingbuild-lod → RAD level-of-detail tree–
RADGaussian splats (Spark), streamed: header, then chunks of the tree by range requests––
LIF · TIFF · OME-TIFF · LSM · PNG/JPEG/BMP slicesVolume, ray-marched; only the stack shown is read, in a Web Worker (from the file, or by range requests)8-bit volume and a maximum intensity thumbnail–
NRRD · NIfTI · MetaImage · MRC · VGI · XTEKCTVolume, ray-marched; only the stack shown is read, in a Web Worker (from the file, or by range requests)8-bit volume and a maximum intensity thumbnail–
DICOMUncompressed series from a ZIP: CT in Hounsfield units, with the files' and the usual windowspydicom, also JPEG, JPEG 2000 and multi-frame → volume; never patient data in the result–
ABC · BLEND · X3D · GML–Blender → GLB–
STEP / STP · IGES / IGS–OpenCASCADE → GLB–

Converted models are compressed with gltfpack and get a light preview that loads first; point clouds get a shuffled preview and a streamed octree, Gaussian splats a streamed level-of-detail tree, image stacks an 8-bit volume. Uploads can be ZIP, RAR or tar archives with textures and material files.

Where it runs

The same viewer, configured by one settings file or by the manifest itself.

In a repository

A Drupal module for WissKI: models on entity pages, conversion on upload, annotations saved back.

On your server

Docker images for the viewer and worker, with profiles for test, development and drag-and-drop sandbox.

In any page

An embed snippet with presentation mode, autorotation and a chosen camera. Settings follow the manifest. For the model alone, ?ultralight=1.

On a phone

Android and iOS builds of the same viewer, for fieldwork and teaching.

Three weights of the same viewerNew

What a visitor downloads before the model itself, compressed: the viewer's code, styles, fonts and the light the model is shown in.

Full

≈ 2.0 MB

Every tool, with saving to the server, the publishing checks and the file download.

Lightweight

≈ 1.2 MB

The same tools for viewing, without saving or downloads. Its light now comes from a 100 KB environment map instead of 1.4 MB, and the model looks the same.

viewer.lightweight

Ultralight

≈ 0.27 MB

The model and nothing else: no menu, intro or gallery, only turning and zooming. glTF and GLB, compressed or not, lit as in the other two.

?ultralight=1 · ultra.html

Why ultralight

The model sooner. Seven times less to download than the full viewer and four times less than the lightweight one: on mobile data the model is on screen seconds earlier.

Many objects on one page. A collection or a catalogue can show a model in every entry without each one bringing the whole viewer.

Nothing between the visitor and the object. No menu or intro: for museum labels and QR codes, kiosks, learning platforms and articles.

Less traffic. Smaller transfers for the visitor's data plan, the server and the CDN, and less work for the phone.

One parameter. ?ultralight=1 on an existing viewer link opens it with the same model and options; ultra.html can be linked directly too.

Try it

Two public instances of the viewer, beside the main one: one for your own model, one for the example manifests.

Sandbox

Drag and drop a 3D model into the viewer and try every tool on it: scan views, sections, measurement, annotations.

explora4d.eu/sandbox Open the sandbox

Testing environment

The newest build of the viewer, with the example AIM3D and IIIF manifests: from scan views and the 4D timeline to the certainty view.

explora4d.eu/testing Open the manifests

Mobile

The same viewer in your pocket

The Android and iOS app is built from the same code as the web viewer, so it has the same tools: scan views, raking light, sections, measurement, annotations, the certainty view and IIIF manifests. Models and point clouds come from ExHUB, the shared repository, or from the device itself.

ExHUB
The shared repository of the project's models and point clouds, converted on upload: meshes as compressed glTF, large scans as streamed 3D Tiles.
On the device
Models picked from the phone, and models saved from ExHUB, stay on the device and open without a network.
Examples
The example manifests, from scan views to the certainty view, to try every tool.

One Models button switches between the three. The app reaches ExHUB at an address you can change, so a project can point it at its own repository.

What the phone adds

AR in your room
The model as it is on screen, with its materials and your changes, stands at its real size on the floor or a table, through ARCore, right in the app. On Android for now.
Motion look
Turn the phone and the view turns with it, as if the screen were a window onto the model. Dragging and pinching still work, and the motion carries on from the new view.
360° video
The camera goes once round the model and the app records it as a short video, ready to share in a messenger or by mail. AR, motion look and the video sit together at the end of the navigation bar, one tap away.

Pro+ AR and motion look come with the Pro, Business and Enterprise plans; on the Free plan the video carries a small ExPlora4D mark. See Plans.

QR code for the app on Google Play
Get it on Google Play Android
QR code for the app on the App Store
Download on the App Store iPhone and iPad

Scan a code with your phone's camera, or tap a badge.

On the phone

  1. The welcome screen: the synagogue assembles itself from its wireframe
    Welcome
  2. The Wołpa synagogue in the app, the toolbar above the bottom bar
    The viewer
  3. A section plane cuts the synagogue lengthwise, the cut filled red
    Section plane
  4. The Tempietto in a thunderstorm, rain running down its walls
    Weather
  5. The first stop of a night tour: numbered annotations and the stop's text
    Guided tour
  6. The Look sheet: lights, weather, seasons, sounds, the suggested scene and the ground
    Look

Room for the model on a tablet

On an iPad or an Android tablet held sideways, the app is laid out like the web viewer: the toolbar along the bottom, and the tools in windows beside the model rather than in sheets over it. Sections, weather and guided tours work as on the phone, with more of the building in view.

  1. The synagogue on a tablet held sideways, the toolbar along the bottom
    On its side
  2. The Section planes window beside the synagogue cut lengthwise
    Section plane
  3. The synagogue in falling snow, its roofs white
    Snow
  4. A night tour on a tablet: the stop's text in a window beside the model
    Guided tour

Plans

Viewing is free. The paid plans take away the ads, add the phone's own tools, the repository and the AI assistant, and, for institutions, a setup made to measure.

Free

0 €

  • All viewing tools: scan views, sections, measurement, the certainty view
  • Models from the device and the examples
  • Ads in the app; three tries of AR

Pro

20 € one-time purchase

  • No ads
  • AR in your room and motion look
  • 360° videos without the mark

Enterprise

Individual price agreed with you

  • Everything in Business, the AI assistant included
  • Your own server or repository, set up with you
  • Limits, storage and AI usage agreed for your project
  • Support, onboarding and training for your team
Contact us

Pro and Business are bought in the app (Google Play, App Store), where the price shows in your currency. Enterprise is set up on your account after we agree the scope.

Author

Daniel Dworak

3D web developer · DevOps Team Lead · 16+ years

  • 3D visualization
  • Clean architecture
  • CI/CD
  • Containers
  • Observability
  • Security

Hi, I'm Daniel. I build high-performance web applications with a focus on 3D visualization, interaction and clean architecture, and I'm a DevOps Team Lead with 16+ years of experience designing, automating and operating scalable infrastructure.

My background spans CI/CD, containerized platforms, observability and security. I lead teams, mentor developers and work across multinational, cross-functional groups, representing technical teams, facilitating decisions and aligning engineering work with business goals.

I care about reliable, secure, automated platforms and a culture of ownership, knowledge sharing and continuous improvement.

Stop flattening 3D. Share the ExPerience.

Open the Wołpa synagogue and try every reading

The example collection includes the scan views, raking light, contour lines and the certainty view, each as a manifest you can download and change.