What stored bytes mean
Storage Lanes
Stored bytes support different jobs: public display, source editing, import verification, published playback, dependency stability, or operation memory.
Storage lane explanation for Vibecodr public media, source, and runtime files.
Implementation focus
Use this before deleting stored material, cleaning up imports, or deciding where an app should keep files and data.
Expected outcomes
- Recognize public media, source, staged uploads, and runtime artifact lanes.
- Clean up storage without breaking live work or remix history.
- Avoid treating public metadata as private storage.
- Choose a better data surface when files are not the right tool.
Stored things have different jobs
Storage is not one user-visible folder. Vibecodr stores public media, editable source, staged uploads, published runtime artifacts, deterministic dependency bytes, logs, and operation memory in different lanes because each lane has different visibility, lifecycle, and safety rules.
A storage page should help users understand consequences without asking them to manage platform internals. The practical question is what the object is for: public display, runtime playback, source editing, import verification, or backend operation safety.
- Public media includes cover images, avatars, and other viewer-facing assets.
- Editable source supports Studio, remixing, and version history.
- A runtime artifact is the immutable playback output for a published cut.
- Staged uploads are temporary project bytes waiting for verification/import.
Cleanup must preserve live work
Safe cleanup starts by identifying what still supports a live vibe, remix history, public media, or a pending import. Deleting the wrong object can make an app harder to edit, remix, or explain even if the current player route still opens.
When in doubt, use product cleanup controls instead of trying to treat stored objects as raw files. Product controls can explain what is safe to remove and what is protected by release, source, or public media ownership.
- Remove abandoned staged uploads when an import will not continue.
- Review old public media before deleting covers or thumbnails.
- Keep source needed for remix, rollback, or team handoff.
- Do not store app records or secrets in public metadata to avoid quota rules.
Example and read next
Example: you are cleaning up old projects. Remove abandoned staged uploads and unused media first, then preserve runtime artifact, source, and public media needed by live vibes or remix history.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: Plans, Limits & Quotas
- Read next: Public Assets & Runtime Files
- Read next: Data Surfaces
- Read next: Source & Versions