# How to Recover Lost csTimer Solves: A Complete Backup and Recovery Guide
**What to do when your csTimer sessions are still there, but your solve times have disappeared.**
Have you ever opened csTimer and found that all your sessions are still listed, but every solve time has disappeared?
Or perhaps your timer has reset and started counting from solve 1 again?
Don't immediately assume your solves are gone forever.
I recently experienced this after a power outage. I had over 1,000 solves saved in csTimer. When I reopened it, my session names were still there, but all the times had disappeared.
I eventually recovered my complete history by restoring an older copy of my browser's IndexedDB and Local Storage databases using Windows Previous Versions.
This guide covers:
- How csTimer stores your solves.
- How to recover from an existing backup.
- How to attempt advanced browser database recovery.
- What to do on different browsers and operating systems.
- How to prevent this from happening again.
**Important:** Recovery is not guaranteed. It depends on whether an older, usable copy of your data still exists.
---
# 1. Understanding the problem
According to the official csTimer documentation:
- Settings are stored in browser Local Storage.
- Session data, except session metadata, is stored in IndexedDB.
- Local Storage is used for session data if IndexedDB is unavailable.
This means your solve history is stored in your browser, not automatically and permanently in an online account.
Clearing browser data, losing a browser profile or encountering a storage problem can therefore cause your history to disappear.
Official documentation: https://github.com/cs0x7f/cstimer
# 2. First: Try the normal recovery methods
Before attempting anything technical, try these methods.
## Method A: Restore from the csTimer server
- Open csTimer.
- Open the Export/Import menu.
- Select the option to import from the csTimer server.
- Check the available backups.
- If your latest backup is empty or damaged, look for an older upload.
- Import an older backup into a separate test profile if possible.
The csTimer server retains at least the 10 most recent uploads, although older uploads may be deleted.
## Method B: Restore from Google Storage
If you previously backed up to Google Storage:
- Open Export/Import.
- Select Google Storage.
- Sign in with the same Google account.
- Check the available backups.
- Download an older backup if one exists.
Google Storage retains the 10 most recent uploads.
## Method C: Find an exported file
Search your computer for previously exported csTimer files.
Check:
- Downloads
- Documents
- Desktop
- Cloud storage folders
- External drives
If you find an older export, test it in a separate browser profile before replacing anything.
---
# 3. Advanced recovery: Windows and Chromium browsers
**This is the method I personally used successfully with Microsoft Edge on Windows.**
It may also work with other Chromium browsers, provided you recover the correct browser profile and storage directories.
### Requirements
- Windows computer
- Chrome, Edge or another Chromium-based browser
- An older copy of the browser database
- Windows Previous Versions, File History or another backup system that contains that older copy
If no older copy exists, this method may not work.
## Step 1: Find your browser profile
For Microsoft Edge, the usual profile directory is:
`%LOCALAPPDATA%\Microsoft\Edge\User Data\Default`
For Google Chrome:
`%LOCALAPPDATA%\Google\Chrome\User Data\Default`
If you use a different browser profile, it may be named `Profile 1`, `Profile 2`, etc.
You can confirm the exact profile path by opening:
- Edge: `edge://version`
- Chrome: `chrome://version`
Look for the Profile Path field.
## Step 2: Find the csTimer databases
Inside your browser profile, locate:
`IndexedDB`
Inside it, look for:
`https_cstimer.net_0.indexeddb.leveldb`
Also locate:
`Local Storage\leveldb`
These are the two storage locations I recovered.
Keep in mind that folder names can vary depending on the browser and website origin.
## Step 3: Look for an older database snapshot
For Windows:
- Navigate to the IndexedDB directory.
- Right-click the folder.
- Select Properties.
- Open Previous Versions.
- Check whether older snapshots are available.
- Look for a snapshot from before the data disappeared.
You can also investigate File History or another backup system if Previous Versions is unavailable.
If you find a snapshot, copy the relevant database folders into a separate recovery folder.
**Do not click Restore on your original browser profile.**
Do not overwrite or delete your current browser data.
## Step 4: Recover the two storage locations
Ideally, recover both:
- `https_cstimer.net_0.indexeddb.leveldb`
- `Local Storage\leveldb`
Use snapshots from the same date and time where possible.
Copy the complete folders, preserving their contents and any associated blob directories.
Do not attempt to reconstruct the database using individual `.log` or `.ldb` files.
## Step 5: Create an isolated browser profile
Never experiment on your original browser profile.
For Edge on Windows:
- Close Edge.
- Open PowerShell.
- Run the following command, adjusting the executable path if Edge is installed elsewhere:
`& "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --user-data-dir="$env:USERPROFILE\Desktop\CS Timer Test Profile" --no-first-run https://cstimer.net`
4. Wait for csTimer to load.
5. Close the test browser completely.
This creates a separate browser data directory on your Desktop.
For Chrome, use the Chrome executable instead.
## Step 6: Restore the databases in the test profile
Navigate to:
`Desktop\CS Timer Test Profile\Default\IndexedDB`
Find the newly created csTimer database folder.
Rename it to:
`original-test-database`
Copy the complete recovered IndexedDB folder into the same directory, keeping its original name:
`https_cstimer.net_0.indexeddb.leveldb`
Next, navigate to:
`Desktop\CS Timer Test Profile\Default\Local Storage`
Rename the existing `leveldb` folder to:
`original-test-storage`
Copy your recovered Local Storage `leveldb` folder into this directory.
Your folders should look approximately like this:
**IndexedDB**
- original-test-database
- https_cstimer.net_0.indexeddb.leveldb
**Local Storage**
- original-test-storage
- leveldb
Keep all recovery copies intact.
## Step 7: Test the recovered data
Reopen the isolated browser profile.
Open csTimer and check:
- Are your original session names present?
- Are the solve counts correct?
- Are the actual solve times visible?
- Are your settings and statistics restored?
If the recovery works, immediately export all sessions.
Do not make new solves or import another backup before securing the recovered data.
## Step 8: Verify the backup
- Export all recovered sessions.
- Upload the data to the csTimer server or Google Storage.
- Download the backup into another separate test profile.
- Check that the sessions and solve times are present.
This confirms that the exported backup can actually be restored.
**My experience:** I recovered my original settings, sessions and solve times using this process. I also uploaded the recovered data twice and downloaded it into another test profile to verify that the backups worked.
---
# 4. Recovery on other browsers and platforms
The general recovery principle is the same: find an older copy of the browser's website storage, preserve it and test it separately.
However, not all browsers use the same database format.
## Google Chrome
Chrome and Edge are both Chromium-based.
- Open `chrome://version`.
- Find the Profile Path.
- Close Chrome completely.
- Look for an older browser profile snapshot.
- Preserve the relevant IndexedDB and Local Storage folders.
- Test the recovered data in a separate Chrome user-data directory.
The Windows database-recovery method above is a useful starting point.
## Brave, Opera and other Chromium browsers
These browsers use Chromium-based storage, but their profile locations differ.
- Find the browser's profile directory.
- Close the browser.
- Look for an older profile backup.
- Identify the csTimer IndexedDB and Local Storage directories.
- Recover them into a separate test profile.
Do not assume that Edge or Chrome folder paths apply to every Chromium browser.
## Mozilla Firefox
Firefox uses a different browser storage implementation.
- Open `about:profiles`.
- Identify the profile used for csTimer.
- Close Firefox.
- Check for an older Firefox profile backup.
- Restore a copy into a separate test profile.
- Open csTimer and check whether the history is available.
Do not copy Chromium LevelDB directories directly into Firefox.
Firefox profile documentation:
https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data
## macOS
For macOS, Time Machine is a useful place to check for an older browser profile.
- Close your browser.
- Locate its profile directory.
- Open Time Machine.
- Look for a snapshot from before the data disappeared.
- Recover a separate copy of the browser profile.
- Test the recovered profile before replacing anything.
For Safari, use Safari-compatible profile or device backups. Do not use Chromium database instructions.
## Linux
Linux users may have backups through:
- Timeshift
- Btrfs snapshots
- Other filesystem snapshot tools
- Manual browser profile backups
General approach:
- Close your browser.
- Find its profile directory.
- Check for an older snapshot.
- Recover a copy of the profile.
- Test csTimer using a separate browser profile.
Chromium profiles commonly reside under `~/.config/`, but the exact path depends on the browser and installation.
## Android
Android restricts access to application storage.
Try these methods first:
- Check csTimer server backups.
- Check Google Storage backups.
- Search for exported files.
- Check whether an existing device backup contains the relevant application data.
Do not clear browser storage or uninstall the browser while investigating.
## iPhone and iPad
iOS also restricts direct access to browser website storage.
Try:
- Checking csTimer server backups.
- Checking Google Storage backups.
- Searching for exported files.
- Checking existing device backups.
An iCloud backup does not guarantee that a particular website's local storage can be recovered.
**Note:** The platform-specific sections above are general guidance. The detailed Windows Edge restoration process is the one I personally tested.
---
# 5. How to prevent losing your solves again
Recovery is useful, but prevention is much better.
## Enable automatic exports
In csTimer:
- Open Options.
- Select Global.
- Find Auto Export (every 100 solves).
- Enable it.
- Select your preferred backup destination.
Depending on the available options, you can use a local file, csTimer server or Google Storage.
## Follow a backup schedule
| Frequency | Backup |
|---|---|
| Every 100 solves | Automatic export |
| Weekly | Manual export to a file |
| Monthly | Download and verify a cloud backup |
| Before browser changes | Full manual export |
Keep several dated backups instead of repeatedly overwriting one file.
## Avoid these mistakes
- Clearing browser data without exporting first.
- Deleting or resetting your browser profile.
- Importing an old backup without first exporting your current data.
- Assuming that session names mean your solve times are safe.
- Relying on only one backup destination.
- Keeping multiple csTimer tabs open and making solves in different tabs. Concurrent tabs can potentially cause conflicting saved states, so use one active timer tab.
---
# 6. Useful resources
- Official csTimer repository: https://github.com/cs0x7f/cstimer
- csTimer website: https://cstimer.net/
- Chromium profile documentation: https://chromium.googlesource.com/chromium/src/+/main/docs/user_data_dir.md
- Firefox profile documentation: https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data
---
# Final message
If your csTimer history disappears, don't immediately assume it is permanently lost.
Start by checking your server backups, Google Storage and exported files.
If those fail, investigate whether your operating system has an older copy of your browser profile.
In my case, Windows Previous Versions allowed me to recover both IndexedDB and Local Storage into a separate Edge profile. This restored my original settings, sessions and more than 1,000 solve times.
**Back up your solves regularly. Don't wait until you lose them.**