Checkpoint vs JKSV

Updated 2026 · ~5 min read

The two go-to Switch save managers (backup / restore / share) are Checkpoint (FlagBrew) and JKSV (J-D-K). They cover the same category but with opposite design philosophies — pick wrong and your daily workflow becomes a quiet source of friction.

Fast & simple

Checkpoint

  • Long-running, dating back to 3DS days
  • Two-button workflow: L (backup) / R (restore)
  • 1-second startup, 5-second operations
  • Game grid + backup list UI
Powerful & flexible

JKSV

  • JKSM successor, actively maintained
  • File-level selective copy
  • BIS partitions / system saves supported
  • Many options (compression, naming templates)

Feature comparison

ItemCheckpointJKSV
UI simplicityIntuitiveHeavier learning curve
Startup speed~1 s~3-5 s
User switchingYesYes
File-level selective copyNoCore feature
ZIP compressionNoYes
BIS partition accessNoYes
System saves (news, etc)NoYes
Custom backup naming templatesNoYes
Direct transfer w/o SD removalNoNeeds FTP separately
Cloud uploadNoNo
Update cadence (2026)Roughly monthlyActive

Workflow comparison

Case: backup before a Zelda boss fight

Checkpoint: launch → pick Zelda → L → done. ~5 seconds.

JKSV: launch → pick Zelda → "Backup" menu → name → confirm → done. ~15 seconds.

Case: move only Splatoon's "lobby settings" to another console

Checkpoint: can't — operates on whole-save granularity.

JKSV: launch → Splatoon → enter file browser → select system_data.bin only → Copy → restore that file on the other console. JKSV is the only choice when you need file granularity.

Case: full backup of 100 titles, SD-conscious

Checkpoint: 100 titles × N MB of raw files pile up on SD.

JKSV: enable ZIP and you save 30–50% space. For long-term archive, JKSV.

Neither tool edits saves — they just back up and restore binaries as-is. To change values, use EdiZon.

Cross-compatibility

Both tools fundamentally do the same thing: read raw binaries from the save partition and write them to SD. File format is identical. You can restore a Checkpoint backup via JKSV (and vice-versa), though paths differ so you may need to move files.

SD layout

JKSV uses human-readable title names; Checkpoint uses raw TitleIDs. JKSV wins for opening on PC and recognizing which game is which.

Verdict — pick by use case

Quick daily backups → Checkpoint.

One button, one second, no friction. If you're trying to build a daily-backup habit, friction is the enemy.

File-level control / system saves / compressed archives → JKSV.

The full-feature option for power users. Past the learning curve, more flexible than Checkpoint.

Both works fine too — disk usage is tiny. Use Checkpoint for daily, JKSV when you need precision.

Relation to the secretchat.tel loader

Checkpoint, JKSV, and our loader all run as homebrew NROs under Atmosphère, sharing the same SD. Either save manager is strongly recommended for loader users — insurance against save corruption or hardware failure.

Related