Open-source toolchain and compliance verification system around the Khronos SPZ 3D Gaussian Splatting compression specification
Responsibility Boundary: Does only two things—SPZ→GLB format packaging and GLB delivery workflow
- Core Positioning: Lossless packaging (SPZ compressed stream stored unchanged in GLB)
- Repository: https://github.com/spz-ecosystem/spz2glb
- Live Demo: GitHub Pages
- Key Features:
- WASM memory and API capabilities (pre-allocation, explicit release, statistics and dual-tier configuration)
- Dual-end synergy: browser-side lightweight preview/quick validation; local CLI for heavy-duty conversion/batch processing/deep verification
- Three-layer verification: structure verification / lossless verification / decoding consistency verification
Responsibility Boundary: L2-only SPZ legality checker for validating headers, flags, and TLV trailer extensions without changing baseline SPZ decoding behavior
- Core Positioning: SPZ extension compliance review and compatibility validation
- Repository: https://github.com/spz-ecosystem/spz_gatekeeper
- Live Demo:
- GitHub Pages: https://spz-ecosystem.github.io/spz_gatekeeper/
- CloudBase (China CDN): https://openclaw-spz-3gt7x2sya7c10ef2-1355411679.tcloudbaseapp.com/
- Key Features:
- Validates SPZ header: magic, version, point count, SH degree, flags, reserved
- Validates TLV trailer layout after base payload
- Validates known vendor extensions (e.g., Adobe Safe Orbit Camera
0xADBE0002) - Warns on higher SPZ versions, continues best-effort validation
Experimental Declaration: This is an experimental 3D asset distribution system, aiming to provide the community with an experimental solution using QR codes as a unified carrier for issues such as large file sizes difficult to transfer, high storage costs, fragmented standards causing compatibility chaos, and lack of lightweight instant distribution means.
A QR-code-based full-chain SPZ/GLB distribution and verification system:
┌─────────────────────────────────────────────────────────────────────────┐
│ QR-Code Native Distribution Architecture │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ Data Admission Layer Distribution Auth Layer Consumption │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ SPZ │ │ Gatekeeper│ │ spz2glb │ │
│ │ Dataset │──────────→│ Auth │───────────→│ Web │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ │ │ │
│ ↓ ↓ │
│ Generate QR with Scan-to-Convert │
│ authorization WASM lossless │
│ │ packaging │
│ └────────────────────────┘ │
│ │ │
│ ↓ │
│ GLB Download Delivery │
│ (or QR re-distribution) │
│ │
└─────────────────────────────────────────────────────────────────────────┘
| Phase | Responsibility | Carrier | Status |
|---|---|---|---|
| Admission Check | Gatekeeper L2 legality check | SPZ file | ✅ spz_gatekeeper check-spz |
| Authorized Distribution | Valid SPZ/GLB generates distributable QR | QR Code | 🚧 Gatekeeper built-in generation (planned) |
| Scan-to-Verify | Gatekeeper validates authorization in QR | QR Code | 🚧 spz_gatekeeper verify-qr (planned) |
| Scan-to-Convert | spz2glb web reads QR and converts | QR→SPZ→GLB | 🚧 v3.0 experimental support (planned) |
| QR Re-distribution | GLB can also be redistributed via QR | QR Code | 🚧 Experimental support |
| Scan-to-Render | Browser direct rendering (future exploration) | QR→Render | 🔬 WebGL/Three.js (experimental) |
- Scan-to-Verify: Gatekeeper embeds SPZ file hash and compliance signature in QR; scan first validates then converts, ensuring data source trustworthiness
- Scan-to-Convert: spz2glb web recognizes QR, automatically pulls SPZ and executes WASM lossless packaging to GLB
- QR Re-Distribution: Generated GLB can be repackaged as QR, enabling chain lightweight distribution of assets
- Dataset Admission Baseline: All SPZ data entering the ecosystem must pass gatekeeper validation and generate authorized QR
| Pain Point | Traditional Solution | QR-Code Native System |
|---|---|---|
| Large files, difficult transfer | Cloud drive/email large file transfer | QR lightweight sharing, scan to download/convert |
| High storage costs | Long-term hosting of large files | QR points to object storage, on-demand pull |
| Fragmented standards, compatibility chaos | Various format extensions work independently | Gatekeeper unified validation, only compliant data generates QR |
| Lack of instant distribution | Install dedicated software or plugins | WeChat/Mini Program scan to use, no install needed |
| Poor mobile experience | Large file download crashes, rendering lag | WASM pre-check memory budget,超限引导至 CLI |
- HTTPS Direct Link: SPZ/GLB files pointed to by QR must have CORS configured
- Mobile Memory Budget: 32MB tier, files exceeding limit are directed to CLI processing
- Status: Experimental development, v3.0 experimental release plans scan-to-convert, with scan-to-render as a future exploration
| Project | Documentation | Demo |
|---|---|---|
| spz2glb | Wiki | GitHub Pages |
| spz_gatekeeper | README | GitHub Pages / CloudBase |
The subsequent version roadmap will be published after v2.1 goes live. The current release cadence is quarterly. Version 3.0 is tentatively scheduled for Late Summer to Early Autumn of the Bingwu Year (Q3 2026), and is planned to align with the next phase of the SPZ_2 draft specification (subject to the official release notes).
- spz_gatekeeper - SPZ legality checker
- spz2glb - SPZ→GLB format packaging and distribution tool
- spz-entropy - SPZ entropy encoding optimization (in development)
- KHR_gaussian_splatting - Khronos official 3D Gaussian Splatting glTF extension
- KHR_gaussian_splatting_compression_spz_2 - Khronos SPZ_2 compression extension proposal (current draft)
SPZ Ecosystem is dedicated to developing and maintaining open-source tools for the Khronos SPZ 3D Gaussian Splatting compression specification. Our goal is to make high-quality 3D content compression accessible, efficient, and compatible across the 3D graphics and AIGC industries.
Design Principles:
- Single Responsibility: Each tool does only what is within its defined boundary
- Verifiable: All output must pass standardized validation
- Dual-End Synergy: Browser-side lightweight interaction, CLI for heavy task processing
- QR-Code Native: QR codes as the unified distribution entry point, achieving full-chain closed loop of admission-authorization-consumption, providing an experimental solution for 3D asset distribution dilemmas
We are committed to fostering an open, inclusive, and collaborative community. All participants should abide by our Code of Conduct.
We welcome contributions from everyone! Whether you are a developer, researcher, or industry partner, there are many ways to get involved:
- Code Contributions: Submit pull requests to our core repositories
- Issue Reporting: Help us improve by reporting bugs or requesting features
- Documentation: Improve our guides, tutorials, and API references
- Community Support: Answer questions in discussions and help new contributors
For detailed instructions, please read our Contributing Guide.
- Organization Email: pjhspz2026@outlook.com
- Maintainer: gugu23456789
We actively seek collaboration with industry partners, especially those working in 3D AIGC, digital twin, and real-time rendering fields. If you are interested in becoming a core maintainer or participating in the project, please contact us!
This organization is maintained by the SPZ Ecosystem community and licensed under the MIT License.
Cultural Note: This project is released in the year of the Red Fire Horse (Bingwu, 丙午), Huangdi Era 4723. It honors the ancient Chinese lunisolar calendar, a testament to humanity's enduring quest to harmonize with the cosmos.