{{ heroBadge }}

Your Minecraft world, rendered into a 3D map.

{{ heroYue }}

A from-scratch TypeScript port of BlueMap, the Minecraft world renderer and 3D web map.

Render from a desktop application, or from a GitHub Actions run with nothing installed at all, and browse it in an interface rebuilt from the ground up in Material Design 3.

Read the documentation

This build of the site did not find a published release with a verified installer attached, so it offers no download. Nothing here guesses a URL.

Windows only, and permanently unsigned by choice — SmartScreen will warn. Rendering needs Java, which the app fetches into its own folder.

Which renderer runs today, in one sentence

A world you render locally is rendered by upstream BlueMap's own Java engine, built from the vendored source and driven by the application as a child process. The TypeScript mesher this project exists to write passed its byte-comparison parity gate on 2026-08-04 and still does not render anything in the product. Every render records which engine produced it.

The size of it

A port of a renderer is not one file, and none of these numbers are marketing. Each one is countable from the repository, and the line beneath it says where.

{{ stat.value }}

{{ stat.label }}

{{ stat.detail }}

What it does

Every row is built, unit tested and reachable by clicking. Each links the article that states its behaviour, configuration, failure modes and verification.

{{ f.title }} {{ f.body }} {{ f.status }}

New here? Start with this

Everything above assumes some BlueMap vocabulary already. This does not.

1. {{ step.n }} {{ step.text }}

Two engines, one of them running

Laid out side by side so nobody has to infer which is which.

Renders today

Upstream BlueMap's Java engine

Built from the vendored source and driven by the app as a child process, so a world can be rendered now rather than after the port finishes.

Parity passed · not switched on

The TypeScript mesher

961 of 961 hires tiles equal byte for byte, all 24 lowres tiles equal pixel for pixel, on 2026-08-04. Switching over is a separate change with its own verification.

Phase status

{{ ph.id }} {{ ph.label }} {{ ph.status }}

The application, actually running

Captures taken by the project's own harness in continuous integration, not mockups.

All screenshots

Six actions, shown

Finite walkthrough animations with static reduced-motion fallbacks. They are explanatory media, not deployment proof.

{{ w.title }} {{ w.body }} {{ w.hint }}

Latest release

No verified release for this build

{{ r.tag }} {{ r.text }}

This build of the site did not find a published release with a verified installer attached, so it offers no download. Nothing here guesses a URL. See what changed

{{ l.title }} {{ l.body }}

Documentation

An article for every feature, covering behaviour, configuration, failure modes, security considerations and verification. {{ articleTotal }} articles, straight from the repository's own docs/ folder.

{{ cat.label }}

{{ cat.count }} articles

{{ cat.lede }}

{{ art.title }} {{ art.blurb }}

Screenshots

Captures of the real running application, taken by the project's harness in continuous integration. Nothing here is a mockup or a redraw.

{{ shotsSummary }}

Settings

Every setting is declared once, searchable, exportable and resettable. Six groups; open one to get a focused page rather than a wall of controls.

{{ groupTitle }}

{{ groupDesc }}

{{ sec.title }}

{{ row.label }}

{{ row.desc }}

{{ o.label }}

{{ row.valueLabel }}

{{ row.toggleLabel }}

{{ row.actionLabel }}

Search

Changelog

Every entry is one commit, carrying the full SHA so the claim can be checked. Entries are grouped by the area of the repository they changed — never inferred as feature or fix.

{{ rel.version }}

{{ rel.date }} {{ rel.chip }}

{{ grp.area }}

{{ c.subject }} {{ c.sha }}

History only — this surface never interrupts. Toasts appear at the corner of the running application; what they said is kept here.

That page is not in this build.

The site ships every article it links, so a missing page means the address was typed, guessed or came from an older deployment. Nothing was fetched from anywhere else to find it.