About 3DKit Online
A browser-based publisher for practical 3D workflows
3DKit Online exists to make everyday 3D production tasks easier to understand, validate, and execute in the browser. We publish focused tools and workflow guides for texture preparation, HDR imaging, model inspection, and animation route planning.
Last reviewed: March 26, 2026
Why this site exists
Many teams do not need a full desktop application for every review step. They need a quick way to inspect a file, validate a texture layout, preview an HDR image, or confirm which animation route makes sense before more expensive production work begins.
This site is built around that browser-first validation layer. Each page is intended to solve a concrete workflow question, not just expose a generic utility.
What we cover
The current coverage centers on four areas: texture preparation, HDR and EXR review, browser-side 3D model inspection, and motion-format route planning. We publish both tools and explainers so users can understand when a task fits an online workflow and when it should move elsewhere.
- Texture channel packing, extraction, and PBR setup checks
- HDR, EXR, and UltraHDR preview and export decisions
- GLTF, FBX, VRM, and MMD model inspection in the browser
- Animation route guidance across FBX, BVH, VRMA, and VMD workflows
Tooling principles
We aim to keep tools practical and honest about their scope. Browser tools are best when the task is review, inspection, lightweight transformation, or early-stage decision making.
When a workflow requires deeper rig editing, complex remapping, advanced compositing, or production-grade authoring controls, the page should say so clearly and point users toward the next validation step instead of pretending that the browser page is the entire pipeline.
- Prefer local, in-browser processing where possible
- Describe supported formats and obvious boundaries up front
- Link tools to guides so users understand why a workflow exists
- State when the next step should move into a DCC, engine, or downstream pipeline
How content is maintained
We update pages when a workflow becomes clearer, a tool gains new scope, or a guide needs stronger examples, caveats, and follow-up links. The goal is not to publish large amounts of filler content. The goal is to make each page more useful to someone solving a real production problem.