How to import your csTimer solves
Cubeathon guide · Reviewed October 2026
You can bring your csTimer history into Cubeathon in two steps: export a file from csTimer, then import it. Each csTimer session arrives as its own session on the right puzzle, with times, penalties, scrambles, comments and dates.
The import runs in your browser and adds the solves to your history on this device. You don't need an account. When it finishes, Cubeathon tells you exactly what it imported and anything it had to skip.
1. Export from csTimer
- Open csTimer in the browser where your solves are.
- Open File → Export and choose Export as file.
- Save the file somewhere you can find it. It's a JSON file containing every session.
Export the whole history, not a single session, so every session comes across with its name and puzzle.
2. Import into Cubeathon
The importer is in two places; both do the same thing:
Choose the file you exported. The page reloads and shows a summary, for example “Imported 240 solves into 3 sessions from csTimer”, followed by a note on anything that was adjusted or skipped.
What carries over
- Every solve time
- Exactly as recorded.
- +2 and DNF
- Kept as penalties. A DNF keeps its measured time, as in csTimer.
- Scrambles
- Attached to each solve.
- Comments
- Become the solve's note.
- Dates
- Each solve keeps the date and time csTimer recorded.
- Sessions
- Each csTimer session becomes a Cubeathon session with the same name, on the matching puzzle.
How puzzles are matched
Cubeathon reads each session's scramble type in csTimer. Training variants go to their physical puzzle: one-handed, blindfolded or PLL-practice sessions on a 3×3 become 3×3 sessions. A session with no puzzle information is treated as 3×3, which is what csTimer itself does.
What's adjusted or skipped
Nothing is changed silently. Each of these is counted and reported in the summary:
- Sessions for puzzles Cubeathon doesn't support are skipped, and the summary names the puzzle types.
- Split times and reconstruction data aren't stored; the total time is kept.
- Penalties other than +2 are added to the time and noted on the solve.
- Solves without a date are dated on the day you import them.
- Solves already imported are skipped, so importing the same file twice doesn't duplicate anything.
- Unreadable records are skipped and counted.
After the import
Switch to a puzzle and open its session menu: your csTimer sessions are listed by name. In the Solves list each imported solve carries an Imported tag.
Imported times don't set PBs or averages
Cubeathon's personal bests and averages count only solves timed on Cubeathon's own timer. Your csTimer solves stay in your history with their scrambles and notes, but they don't become a Cubeathon PB, and they can't be shared as a result. That keeps every Cubeathon record something the app actually saw happen.
Check it came across
- Compare the solve counts with csTimer, session by session.
- Open one +2 and one DNF and check the penalty is there.
- Make a fresh Cubeathon backup so the imported history is saved in one file.
If the import fails
- “That file isn't valid JSON” — the file isn't a csTimer export. Export again with File → Export → Export as file.
- “No csTimer sessions found” — the file has no sessions in it; make sure you exported from the browser that holds your solves.
- “Couldn't be saved — this device's storage may be full” — free up browser storage and import again; solves that already made it across are skipped the second time.
Moving from another timer in general? The blog post on switching cube timers without losing your history covers what to check before you switch.