If Rebit says your account storage is full, open Profile > Settings > Storage and inspect the file-type breakdown. Clearing browser or app data does not free cloud storage. To reduce account usage, remove unwanted files from the account itself, after downloading anything you want to keep.
There are two different storage problems that can look similar: your Rebit account can be near its limit, or the device running the browser can be short of space. Start by identifying which one is reporting the problem. Otherwise, you can lose local data without making room for the upload you were trying to finish.
Account storage and device cache are different
Rebit's Storage and Pro manual lists ROM files, imported games, manual and automatic saves, in-game saves, screenshots, and profile banners as account storage. The local ROM cache helps games load faster on the current device and is managed separately.
| What you observe | Check first | Avoid assuming |
|---|---|---|
| Rebit reports an account storage limit | Profile > Settings > Storage | Clearing browser data will reduce account usage |
| Your operating system reports low device storage | The device's storage report and download destination | Deleting a Rebit library entry is the right way to clear device space |
| Uploading or saving fails without a clear storage message | Account usage and the connection, plus the exact error | Every failed save means the account is full |
| The same account looks full on another device | The account's storage breakdown | Switching phones gives the account a separate allowance |
The current manual also states that Settings has no standalone ROM Cache cleanup page. Do not search for an old menu instruction or clear the whole app as a substitute. Clearing local data can remove device-only data and pending replay uploads.
Calculate how much space the upload actually needs
The number that matters is remaining account space compared with the incoming file, not the free space on your laptop. Downloading a backup gives you another copy; it does not remove the account copy or reduce usage.
Use the values shown in Storage and the size of your intended upload:
- Remaining space: subtract current usage from the account limit.
- Minimum cleanup: subtract remaining space from the incoming file size.
If minimum cleanup is negative, the account has enough room for that file by this calculation. Investigate the actual error instead of deleting more games. Leave some additional space for the saves and screenshots you plan to create; filling the account to the exact limit is not a useful stopping point.
Worked example — illustrative, not a measurement of a Rebit plan: your account has 180 MiB remaining and the file you want to upload is 420 MiB. You need to recover at least 240 MiB for that file alone.
| Candidate cleanup | Space recovered in this example | Enough for the upload? |
|---|---|---|
| Ten unwanted screenshots at 2 MiB each | 20 MiB | No; 220 MiB still missing |
| Thirty obsolete states at 10 MiB each | 300 MiB | Yes; about 60 MiB remains afterward |
| One unused 500 MiB game file | At least 500 MiB, before related content | Yes, but deleting the game also deletes related saves and screenshots |
Actual state and image sizes vary. The point is to choose a category that can cover the gap, then verify the real usage after cleanup. A large game is not automatically the best deletion: thirty disposable checkpoints may be less costly to lose than one unfinished campaign.
Use the same units for both sides of the calculation. A rounded usage percentage is useful for spotting a nearly full account, but it is too imprecise for deciding whether a file will fit with only a few megabytes to spare. Read the available size values and allow headroom instead.
Pick a cleanup that preserves the thing you care about
- Keeping a campaign, losing redundant checkpoints: keep the game entry and download the saves you want. Remove selected old saves rather than the whole game.
- Finishing with a game but keeping progress for later: archive the matching game files and important saves separately, check the downloads, then remove the library entry.
- Keeping everything online: investigate the current plan options rather than deleting data you still need. No upgrade is required to follow the backup steps below.
Change one small batch first. Reopen Storage and compare the new usage with the value you recorded. If the number does not move as expected, stop there; repeated deletion is not a diagnostic technique.
Keep the progress before removing the game
Deleting a library game also removes its related saves and screenshots. It is not an archive command that preserves your playthrough for a later re-upload.
Before removing a game you may return to:
- Open its game details page and use Manage saves.
- Download important in-game saves and any manual states you intend to keep.
- Keep the original game file, or use Download ROM File if you need your own copy from the library.
- Check that the downloads finished and that you can locate them outside Rebit.
- Keep enough context to identify the game release and the save type later. For multi-file games and bundled saves, retain all required files.
A downloaded state is not a promise of compatibility with another core or game revision. If you need to prepare fresh progress, use the game's save menu, then Rebit's Export In-Game Save, and finally the save's download action for a separate device copy. The save manual explains those distinct steps and the different multiplayer save controls.
If you cannot download the files you need, pause the cleanup. Deleting the entry first would remove the very data you are trying to protect. This guide does not assume there is a restore-from-trash option.
Trim old saves without deleting the whole library entry
When the game itself is still useful, work on its unwanted saves or screenshots instead of removing the entire entry. Open Open Saves while playing or Manage saves from the game page. Download important checkpoints, then use the delete action only on saves you have decided to discard.
Keep checkpoints for their purpose, not only their age. An older manual state before a difficult section may be more useful than several recent automatic states. The newest timestamp alone does not establish that a save contains the progress you want.
For screenshots, use the game's gallery selection controls to remove your unwanted images. There is no need to delete the game just to clean up screenshots.
Then review Max Auto Saves under save settings. A lower retention setting can help limit future accumulation; do not assume changing it has already removed every older save. Inspect the existing list and Storage again. Autosave availability varies by core and play mode, so verify the controls offered for the session you actually use.
Prove cleanup worked before deleting anything else
Your success check has three parts: account usage decreased, the intended upload finishes, and the important backup files are still present outside Rebit. Check each separately.
Once you have made room, retry one intended upload and note the exact outcome. If it still fails despite available account space, record the error text, file size, system, device, and browser or app version. Avoid repeatedly deleting files based on the same untested assumption.
If you want to keep the whole collection in the account, review the current plan options in Settings rather than deleting useful progress under pressure. This is a choice about how much you want to store, not a substitute for investigating a failed transfer.
For the upload workflow itself, see upload your own ROM and play online. Rebit does not provide copyrighted ROM downloads; bring legally owned game files. For ongoing cloud-save use, keep the account copy and a separate backup distinct: freeing space should leave you knowing where your important progress still lives.
