Skip to content

docs: explain how branches, checkpoints and builds affect storage - #1307

Merged
willeastcott merged 2 commits into
mainfrom
docs-storage-version-control
Oct 29, 2026
Merged

willeastcott merged 2 commits into
mainfrom
docs-storage-version-control

Conversation

@willeastcott

@willeastcott willeastcott commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Support requests this month showed that users can't work out from the docs why their storage grows, or how to reduce it. This PR fixes the storage and version control pages:

Version control overview

  • Removes "Branches cannot be deleted", which contradicted the Branches page.
  • Rewrites "How Version Control Affects Your Storage":
    • Every open branch counts its own full copy of the assets, even when files are identical to other branches.
    • Closing a branch is the main way to reduce usage.
    • Deleting a branch (after closing it first) and hard reset also free checkpoint storage.

Branches

  • Closing a branch removes its asset copy from storage usage, but keeps its checkpoints.
  • Explains how to reopen a closed branch: the Closed filter, then "Re-Open This Branch".
  • Merged branches can only be closed, not deleted.
  • Deleting a branch frees its checkpoints. Users are told to close the branch first, because deleting a branch that is still open doesn't currently free its assets.

Checkpoints

  • Clarifies that a checkpoint restores the whole project but only stores the changes since the previous one.
  • Hard reset frees the deleted checkpoints' storage.

Account settings, Usage

  • Separates project counts from storage.
  • Lists which categories count towards the allowance: Assets, Apps, Code and Checkpoints.
  • Notes that deleting a published build frees its full size.
  • Clarifies that SuperSplat splats don't count towards the allowance.

Includes the Japanese translation. markdownlint-cli2 passes on all changed files.

🤖 Generated with Claude Code

The version control overview said branches can't be deleted, which
contradicted the Branches page, and its storage section only listed
deletion as a way to reduce usage. Explain that every open branch counts
its own copy of the assets, that closing a branch removes that copy from
usage (and reopening restores it), and that deleting a branch or doing a
hard reset also frees checkpoint storage. Document how to reopen a closed
branch, and that merged branches can only be closed.

On the account page, separate project counts from storage, list which
categories count towards the allowance, note that deleting a published
build frees its size, and clarify that SuperSplat splats don't count.

Includes the Japanese translation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deleting a branch that is still open removes its checkpoints but doesn't
currently free its assets from storage usage. Recommend closing the
branch first instead of promising that deletion frees both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@willeastcott
willeastcott merged commit 5ce1568 into main Oct 29, 2026
4 checks passed
@willeastcott
willeastcott deleted the docs-storage-version-control branch October 29, 2026 11:11

This branch was successfully deployed

1 active deployment
Preview — ae0c3698 Deployed Oct 29, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant