1. How Local-First IndexedDB Storage Works
Unlike cloud coding environments that require user accounts and store your source code on remote servers, GB Coder persists your entire workspace tree locally in your browser’s IndexedDB database named gb-coder-projects-db. This ensures zero latency on load and complete code privacy.
2. Exporting ZIP Archives with SHA-256 Hashes
When you click Export Project, GB Coder packages all files, folders, and metadata into a standard ZIP archive. As part of this process, the engine calculates a SHA-256 integrity hash across all file contents and embeds the verification manifest directly inside the archive.
// Example backup-manifest.json embedded in exports
{
"projectId": "proj-98214",
"name": "Dashboard-Component",
"exportedAt": "2026-10-15T12:00:00.000Z",
"filesCount": 14,
"integrityAlgorithm": "SHA-256",
"checksum": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
}3. Restoring and Verifying Projects Safely
To restore a project, simply drag your ZIP archive into the Projects Dashboard. The import pipeline validates the archive structure, inspects file paths to prevent directory traversal vulnerabilities (such as ../), verifies checksums, and restores the full file tree into a fresh workspace.
4. Best Practices for Long-Term Project Archiving
Because browser storage quotas can be affected by browser profile resets or operating system storage cleanup, we recommend exporting a ZIP backup after concluding major feature milestones. Since exports use standard ZIP formats, you can also extract them directly into VS Code on your desktop.