ALPHA · FAMILIAR WORKFLOW · LIGHTWEIGHT BY DESIGN
Polygonal modelling, refined.
For game artists, students, modders, and independent teams who want the familiar logic of a 3ds Max-style polygon workflow in a fast, focused browser workspace without the premium cost.
THREEVER is in alpha: it is usable and it is being built in the open, but expect rough edges and keep your own backups of anything you care about.

Familiar from day one
Key shortcuts, navigation, and workflows that feel familiar.
Built for game and realtime geometry
The everyday polygon operations, without the scene-suite overhead.
Browser or desktop
WebGPU rendering in a tab, or installed on Windows and fully offline.
Physically based rendering right in the viewport
Mapped PBR shading with studio-style image-based lighting.


THE WORKSPACE
The workflow your hands already know.
The layout follows the mental model many artists already learned: four linked viewports, object and component levels, world and local transforms, editable pivots, command-panel tools, caddies, and modifiers.
- Familiar 1-5 component shortcuts and direct selection
- Grid, angle, and vertex snapping with editable pivots
- Non-blocking geometry edits in a Web Worker
- Undo/redo, autosave, and native session recovery
EDITABLE POLY
Powerful tools. Precise results.
The essential operations are always close, with focused caddies for the values that matter.
- 01
Extrude
Add form from selected polygons, borders, edges, or vertices.
- 02
Inset
Build clean inner faces with group and individual control.
- 03
Bridge
Connect compatible borders and close deliberate gaps.
- 04
Connect
Add edge segments with pinch and slide, or connect vertices.
- 05
Chamfer
Create controlled edge transitions for readable highlights.
- 06
Slice
Cut geometry with an interactive plane and keep modelling.
- 07
Weld
Merge nearby vertices or target a precise destination.
- 08
Subdivide
Preview Catmull - Clark smoothing through the modifier stack.
PRECISION WITHOUT FRICTION
Model with clarity.
Keep spatial feedback and surface decisions visible while familiar precision tools stay close to the model.
- XYZ
Familiar transform gizmos
Move, rotate, and scale in world or local space with readable axis feedback and editable pivots.
- SNAP
Precise snapping
Combine grid, angle, and vertex snapping to place geometry deliberately without breaking flow.
- UVW
Integrated UVW editor
Unwrap, inspect, and refine texture coordinates with a checker view for spotting scale and distortion.
REALTIME LOOK DEVELOPMENT
Materials you can actually read.
Image-based lighting brings shape, metal response, and roughness variation into the modelling viewport without requiring an offline renderer.
- MATERIAL
Mapped PBR
Base color, normal, ambient occlusion, roughness, metallic, and packed ORM maps feed a metallic-roughness pipeline.
- LIGHT
Studio IBL
Switch between Dusk Grassland, Sunset Dunes, and a lean blue/orange Procedural Studio environment.
- VIEW
Per-viewport display
Give every viewport its own shading mode, or apply one mode across the full layout.
- SURFACE
Existing UVs, immediate feedback
Texture maps follow generated and edited UV coordinates, with a checker mode for distortion checks.

SEE IT WHILE YOU MODEL
Judge the surface, not a preview of it.
Physically based shading runs in the viewport under image-based lighting, so highlights, metal response and roughness read while you are still modelling - not after an export to something else.
- Base color, normal, roughness, metallic, occlusion and packed ORM maps
- Every map with its own tiling, offset and UV channel
- Materials shared across objects, so one edit reaches all of them
- Switchable studio environments for judging a surface under different light
A SHORTER MODELLING LOOP
From primitive to portable mesh.
- 01
Block the form
Start with a box, cylinder, or plane and frame it instantly across the viewport layout.
- 02
Edit the topology
Move between components, direct tools, snaps, and world/local coordinates while the worker owns the heavy geometry work.
- 03
Inspect the surface
Unwrap and check UVs, assign texture maps, then judge highlights and material response under selectable IBL.
- 04
Take it with you
Import or export OBJ, export glTF with normals, and rely on local autosave while the document is in progress.

NOW ON THE DESKTOP
The same modeller, installed.
THREEVER now runs as a Windows desktop application as well as in the browser. It is the same editor, the same workflow, and the same files - installed, so it opens from your taskbar and keeps working with no connection at all.
- Works fully offline, with no browser tab and no sign-in
- Asks your machine for its high-performance GPU, which a web page cannot do
- Keeps working while it sits behind another window
- Remembers its window size, position, and maximised state between launches
- Your scenes stay yours: the same OBJ, glTF, and STL import and export
THREEVER KIT · BRING YOUR OWN AGENT
Model with your own agent.
THREEVER also works without a window. The THREEVER Kit is 3D modelling as scripts: a small folder of plain JavaScript that your AI coding agent, such as Claude Code, Codex or Cursor, runs on your computer. The agent writes a short script, runs it, checks the model and looks at a preview picture until it is right, then hands you a .glb file. The editor is there when you want to look at a model or shape it by hand.
Game-ready assets too. The kit's asset pipeline turns detailed models and downloaded packs into light game meshes: fewer triangles, rough shapes with the original look baked on, shared texture atlases, and an approval sheet to check them. To see everything in one run, start the included demo with node examples/demo.mjs and open the sheet it makes.
Your agent, your key. We host no AI and never see your key or your files. The kit runs on your computer and does not go online.
- 01
Download the kit
One small zip. It needs Node.js 20.15 or newer and nothing else, with no installer and no account.
- 02
Open it in your agent
Unzip it and start your agent in the folder. The included AGENTS.md teaches it the modelling scripts, the checks and the conventions.
- 03
Ask for a model
For example:
Make a low-poly wooden stool, 45 cm high, and check it.You get a .glb file. THREEVER imports it (File > Import glTF / GLB) so you can look at its shape or keep editing by hand, and Blender or a game engine shows its colours as well.
MADE FOR THE MODELLING WORK YOU ACTUALLY DO
Familiar capability, focused scope.
Made for game artists
Shape props, level assets, hard-surface forms, and game-ready topology in one focused workspace.
Keep the muscle memory
Quad views, component hotkeys, caddies, pivots, snaps, and a modifier stack feel immediately familiar.
Focused, not stripped down
The high-value polygon tools stay close while unrelated scene-production complexity stays out of the way.
Open and start
A static WebGPU application with browser-side sessions and no mandatory cloud workflow.
PRICING AND ROADMAP
Try now. Follow the roadmap.
Try THREEVER in your browser now. Sign up for free to receive feature updates, roadmap milestones, and product updates as the full release takes shape. Pricing will be announced before release, with accessible plans for independent work, learning, and small production teams.
- NOW
Try THREEVER now
Open the browser workspace today at no cost. Model with the familiar polygon workflow, local project recovery, PBR materials, and IBL. Launch THREEVER.
- NEXT
Offline rendering
Take finished scenes beyond realtime viewport evaluation with a focused offline-rendering workflow.
- PLANNED
Substance integration
Move authored materials into THREEVER through a streamlined Substance material workflow.
- FUTURE
Share and store
Publish content easily across the web and keep projects available through optional cloud storage.
FREE PRODUCT UPDATES
Stay close to what comes next.
Sign up for free to receive THREEVER feature updates, roadmap milestones, and full product news. You can also tell us what you model and which familiar workflows matter most to you.
Prefer email?
GOOD TO KNOW
Questions before you start.
THREEVER is deliberately focused on the polygon workflow. Here is where it fits today.
Who is THREEVER for?
THREEVER is designed for game artists, students, modders, technical artists, and independent teams who need a capable polygon modeller without the weight of a full digital-content-creation suite.
Will it feel familiar to 3ds Max artists?
Yes. THREEVER was born from a practical need. Its creator learned 3ds Max as a primary DCC and wanted the same modelling instincts to carry into hobby and freelance work without the weight of a full production suite. THREEVER preserves the muscle memory that matters, including quad viewports, navigation, shortcuts, component levels, transform gizmos, caddies, snaps, pivots, and an Editable Poly-style workflow. THREEVER is independently developed and is not affiliated with or endorsed by Autodesk.
What do I need to run THREEVER?
In the browser, a current Chromium-based browser with WebGPU enabled, such as Chrome or Edge. The application is fully static and runs from a secure web origin or localhost. The desktop application is a normal Windows install and brings its own renderer, so nothing needs to be enabled first.
What does "alpha" mean for THREEVER?
It means the application is usable and being actively developed, not that it is a preview you cannot rely on. Every release is tested before it ships, and the polygon, UV and material workflows are complete enough to do real work with. It also means things will change, some of them visibly - features are still being added, details still move, and you may find bugs. Please export or save your work to a file you control rather than relying only on autosave, and tell us what breaks - during alpha that feedback shapes what gets built next.
Will my files still open later?
Scenes save as ordinary files you keep, and we take care that a project saved in one version opens in the next. During alpha we cannot promise that for every change, so export anything important to OBJ or glTF as well - those are open formats that any tool can read, and they are not going anywhere.
Is there a desktop version?
Yes. THREEVER runs as a Windows desktop application built from the same editor as the browser version, so the workflow, shortcuts, and files are identical. It works fully offline, asks your machine for its high-performance GPU, and keeps its window size and position between launches. You can download it now from itch.io.
Can I use THREEVER with my own AI agent?
Yes, with the THREEVER Kit. It is THREEVER's modelling code as plain JavaScript scripts that an AI coding agent runs on your computer with Node.js. The agent builds models in code, checks its own results, looks at preview pictures and writes .glb files. It works with your agent and your own key. THREEVER hosts no AI and receives nothing, and the kit does not go online. It is new, so expect it to grow. Models are built in code rather than by hand, and the editor does not show their painted colours yet.
Is THREEVER a renderer?
THREEVER provides realtime PBR and image-based lighting for surface evaluation. It is a polygon modeller and UV workspace, not an offline path-tracing renderer.
Which texture maps are supported?
Base color, normal, ambient occlusion, roughness, metallic, and packed metallic-roughness/ORM workflows are available in the PBR material controls.
Which file formats can I use?
You can import and export OBJ meshes and export glTF geometry with generated normals. Native browser-side sessions provide autosave and recovery while you work.
Ready to start modelling?
Open the workspace, create a primitive, and turn on PBR Material when you want to judge the surface as clearly as the topology.
WHAT'S NEW
Changelog.
18 November 2026 v0.0.98
- Asset Review on big packs and real atlases: Raybike's 894 shipped models check in 3.6 s, not 72 (the table drawn at most four times a second while checks land; each asset's source found once, not searched per row; an asset queued once); the pairwise float check skipped and said for a mesh of more than 150 parts. A halo is the unpadded background - near white or black beside painted texels that are not - so the kit's padding, which takes its colour a little inside the shape, no longer reads as one (Raybike's cut-out atlas 0 %, an unpadded leaf map 42 %); it is checked only where the material cuts. Export: a map is cut out as its material cuts (an opaque material's alpha is data - Raybike's solid atlas's codes - and stays on the opaque atlas); maps known by their data, not their name or length, in the export and in a folder import's sharing
- Docs: PARITY's pack row names Asset > Make LODs
- Asset > Make LODs: an object's lower levels of detail, name@1 and name@2 (RayEngine's names), made with the THREEVER Kit's reduce at a share of its triangles each, previewed beside it and kept as one undo step (a level already there by that name replaced, for the undo too); on the stage with LOD by distance they stand on the object and switch at 14 / 40 m. reduceLevels takes its levels in its options, as the worker hands them
- Asset Review: stage, check and approve a pack in the editor - Import glTF Folder and Import RayEngine Pack (models.bin / pieces.json with their atlases, the kit's readers; a game's file beside its source as "
pack"; materials and maps shared), Asset > Stage (a block per asset - source, results, levels - in shelves on the ground, one undo step), a rider's-eye camera at 5 / 10 / 30 m, a turntable, levels of detail switched by distance as RayEngine culls them (display only), and the Asset Review panel: a row per asset with its triangles per level, materials, map size and memory, the kit's checks in a worker of their own (open edges, those on the ground left out on purpose, floating parts, against its source the outline kept and how far its surface strays; a cut-out map's halo risk; a bake's texels missed) judged pass / warn / fail, Keep / Redo and a note saved with the scene and exported as asset-review.json. Export RayEngine Pack writes textured objects as pieces on padded opaque / cut-out atlases (the kit's packPieces, the format Raybike's medievalView.js loads) beside models.bin. The viewport cuts out at a material's alphaCutoff as a game's alpha test does. Raybike's 894 shipped models stage in 0.8 s; 80 assets check in about 4 s. Tests: the textured pack read by the kit and by Raybike's loader rules and imported back the same, names, layout, LOD distances, judging, the checks (floating parts, holes, halos) - THREEVER Kit c25c507 in the editor (kit branch stage-check, not pushed): the pieces format in memory (shipping.mjs packPieces / unpackPieces, which ship.mjs writePieces is now built on, the demo's files byte for byte as before), a PNG read without Node (pngcore.mjs, every texel as stored) and a models.bin read back in memory (packing.mjs unpackModels), copied into wwwroot/js/kit; io/png.js decodes a PNG exactly with them (the colour under a see-through texel kept, which a canvas loses) and io/streams.js gives zlib and gzip through the browser's Compression Streams
- Asset tools: each opens with the object's own values - half of THIS object's triangles, a cell and a leaf to ITS size - and keeps from the last one only what does not depend on the object (an op names them: Reduce its error and borders, Leaf Plates its spacing and canopy, Rough Shape its method and look, Pad its mode, inset and reach); Rough Shape bakes a map the viewport shows on the default box projection too, not only on an unwrap. Tests: object ops in the caddy (their own preview, commit and cancel, no kernel snapshot, only the named fields remembered), and the controller keeping a clean Reduce as one undo step and refusing one with a hole (original back, the preview freed, nothing on the history)
- File > Export RayEngine Pack (models.bin): every visible object as RayEngine's vertex-coloured pack through the THREEVER Kit's packModels (kit 53819b1: model/packing.mjs, packModels without file IO, now in the editor's copy), each object in its own place in the kit's frame, its colours as display values, objects named name@1 / name@2 its levels of detail, missing normals the kit's auto-smoothed ones; both files into one picked folder (io/files.js saveFilesToFolder). The kit reads back what the editor writes (test), and its audit finds the exported chair closed and outward. Reduce refuses to keep a result that tears the mesh open even when a value was typed and Entered before its preview said so. Tests: the pack, a thinned outline that is no hole, a torn middle that is one (16 checks)
- The Asset menu: the THREEVER Kit's asset tools in the editor, each a caddy with a live preview whose result is kept as one undo step - Reduce (the kit's meshoptimizer reduce: triangles, max error, open borders free or locked; live counts, edges it would tear open shown amber and refused, colour borders, creases and UV seams kept, UV sets carried), Rough Shape and Bake (automatic, voxel cells, height boxes, part boxes, a box or a turned shape, the look baked on and packed into one padded map, the result beside the original, the float and shard checks, the outline and the texels missed as warnings), Leaf Plates (softFoliage and leafPlates on the selected polygons or the whole object: size, spacing, seed, soft or as modelled) and Pad Texture Edges (dilate on the base-colour map, cut-out or opaque); File > Export Scene (GLB, padded textures) pads every base-colour map on the way out. The kit's code runs in a module worker (js/assets: ops.js, kit.worker.js, frame.js for the kit's Y-up metres and its 2.2 colour curve; app/KitBridge.js, app/AssetController.js) with progress, a newer value ending an older run. The caddy gains a note line and object ops whose preview is their own (CaddyController.beginObjectOp); PNGs are written without a canvas (io/png.js), so the colour under a see-through texel survives. A Game Asset rollout on the Modify tab. tests/js/assetTools.test.mjs (15 checks, in npm test): the copy in step with kit/, the policy, the frame, reduce bounds and no holes on the kernel's own meshes, colours and UVs carried, torn edges found, the bake, every shape method, a textured source, leaf plates on a selection only, padding and the PNG round trip. PARITY.md: the kit's code in the editor
- THREEVER Kit b8abbcc in the editor: the kit's browser modules (reduce, proxy, bake, atlas, dilate, foliage, pieces and what they import, with meshoptimizer and its licence) copied into wwwroot/js/kit in the kit's own layout by
node tools/sync-editor-kit.mjs, which refuses a module that imports node: or a package and records the kit commit in wwwroot/js/kit/SOURCE.json; the editor's policy (/app/*, here and in assemble-swa) allows 'wasm-unsafe-eval' so a worker can compile meshoptimizer's WebAssembly (eval and inline script stay refused). Kit b8abbcc (branch editor-tools, not pushed yet): bakeToProxy, voxelProxy, proxyShape and autoProxy tell their progress, bakedPiece passes colorAt (a textured source's look) and progress on; opt-in, every result as before - THREEVER Kit fd7effa: the demo's check in the kit's AGENTS.md says what holds (the yard's colours change on purpose, which outlines must keep 0.9), and the kit's test asserts exactly that
- THREEVER Kit 13636de: the kit's demo -
node examples/demo.mjsmakes the example objects (pine, chair, rock, a small yard pack) and makes each into game meshes with a fitting method (levels and a card, reduce, part boxes and an automatic rough shape with the look baked on, the yard's recipe), one sheet and one report in about 3 s; README, AGENTS.md and CLAUDE.md start with it. The site's kit section names the asset pipeline and the demo. Engine files: RayEngine fb45b26 (main) still has records.js and scatterAnchors.js as of 807f705, byte-identical, so the record is unchanged
14 November 2026 v0.0.86
- THREEVER Kit 28ac70d: the kit's modelling code is its own (moved from RayEngine), and build-kit copies only the two engine files it shares with the games
- THREEVER Kit 678ac1f: glTF's linear vertex colours with { colorSpace: 'linear' } (exportGlb / importScene), used by the kit's examples, so the editor and Blender show kit models as the games do; default output unchanged. build-kit's syncEngine keeps the kit's own change to model/assets.mjs and stops when RayEngine changes that file. PARITY.md: the colour contract settled
- glTF: a white material imports as exactly white, not 0.9999999999999999
- Docs: what the editor and the THREEVER Kit each can do, and what is left to match (docs/PARITY.md)
- Verify tools: headless browsers start muted, speech synthesis included
- Editor: a smooth glTF import stays smooth after its first topology edit
- glTF: material colours written as linear and read back as sRGB, and a material without a base colour factor imports white
- Editor: vertex colours from glTF and the THREEVER Kit, shown, kept through edits, saved and exported
- THREEVER Kit: one kit for the editor and the games, kept in its own repository
- Marketing: the header and footer logos sized again (SWAZM's SiteHeader now names them brand__wordmark and site-footer__logo)
- THREEVER Kit: ship only what git knows, check the examples import into the editor, Node 20.15
- Marketing: the THREEVER Kit section, with the download, three steps and an FAQ answer
- THREEVER Kit: 3D modelling as scripts your AI agent runs, as a download
13 November 2026 v0.0.74
- Privacy policy: state how long hosting logs are kept
- Legal pages for November 2026: accounts in the privacy policy, DDG citations, legal links in the editor
11 November 2026 v0.0.72
- glTF: vertex colours in and out, and the file's asset header on import
- Kernel: weighted corner normals as data, with keep-sharp
- Kernel: edge creases for Catmull-Clark subdivision
- Kernel: optional segments for the box primitive
- Kernel: sphere, UV sphere, cone, torus, lathe and tube primitives
14 August 2026 v0.0.67
- Update SWAZM provider
30 July 2026 v0.0.66
- Type: ask the font for weights it actually has
- Warmer devlog: an invitation rather than a notice
- Shorten the itch devlog to the announcement it is
29 July 2026 v0.0.63
- Add the early-alpha launch devlog for itch.io
- Desktop 0.0.61: the build pushed to itch with the import fixes
- Imported models keep their shading, and their texture goes on the right way
- Desktop 0.0.59: the version the packed build was made at
- glTF: import the half of the format that lives in other files
- Pack: one build in dist, so publish cannot reach for the old one
- One icon for THREEVER, in every place something shows one
- Desktop: the zip extracts to one folder, and the window carries the icon
- Three bugs from testing: the drop, UV redo, and the face tint
- Marketing: the desktop CTA is a download now, because there is one
- Changelog regenerates inside the commit it describes
- Changelog: regenerate at the version this commit carries
- Changelog labels the day it actually ended on; butler failures read as failures
- THREEVER is alpha, and the version numbers now say so
- Add a disclaimer and limitation of liability page
- Desktop: decide on signing - unsigned for now, and correct a stale claim
- The Windows build ships to itch.io, at the version it actually is
- Add PROJECT.md: what THREEVER is, and why it is built this way
- Bring /api/contact home, and let a bought copy keep its attachments
- Fix: a material dropped on the viewport was refused on the way in
- Marketing: announce the desktop application, with a shot of the real thing
- The API to the house C# standards: contracts, not anonymous objects
- Name the modifier and texture-slot strings; look up rather than scan
- Materials are a scene library; every modifier is its own file
- A light is a scene object, so it selects, moves and rotates like everything else
- Cloth is a modifier, through a registry that lets paid modules add types
- Bake is scene-level; the menu bar is the title bar
- Desktop plan: renumber the open list after the icon landed
- Desktop: shell quality, raised GPU limits, itch.io publish
- Desktop build: the same editor, sold once
- Refactor: shared pro modules, extracted subsystems, deduplicated tooling
- Phase 5: realtime cloth, freezable for export
- Phase 4: point and spot lights with realtime shadows
28 July 2026 v0.0.27
- Per-map UV controls, background maps, and GPU baking
- Per-map texture scale and offset
- Drive both sides of the pro gate locally; record where entitlement should live
- Phase 0: the pro seam, with the entitlement actually withholding code
- Plan of record for the pro feature program
- Pro entitlement: server-decided, client-reflected
- Edit Normals: collapse into the mesh, like Subdivision and Symmetry
- Track SWAZM as a submodule here too
- Cover the account controller's failure paths
- Optional accounts in the editor: skippable prompt, menu-bar hint
- THREEVER: send as CONTACT_SENDER, and link back to the request's origin
- THREEVER: declare its own setting names through the shared resolver
278 earlier changes are in the repository history.
