A backup that lives only on the microSD card inside your Switch is one lost card away from being no backup at all. That is why JKSV can upload its backups automatically: it supports WebDAV and a native Google Drive connection, so a copy of every save archive can leave the console as soon as it is created. This guide compares the realistic destinations — pCloud, Koofr, Google Drive, and a self-hosted option — by how much effort they take and how their long-term costs are structured, so you can pick the one you will actually keep using. If you need the software first, you can download JKSV from our download page.
How JKSV Talks to the Cloud
Two connection types cover everything in this guide. WebDAV is a general file-access protocol that JKSV can use with any compatible provider: you give it a server address and login, and uploads happen in the background, with cloud backups stored in ZIP form. Google Drive support is built into JKSV directly and signed in through a limited-input flow designed for a console without a full browser. Both approaches aim at the same habit — automatic, off-console copies — and the best choice depends on which ecosystem you already pay for and how much you enjoy maintaining things yourself.
pCloud: The Set-and-Forget Paid Option
pCloud is the most direct WebDAV route for JKSV, with one condition to plan around: pCloud’s WebDAV access is limited to its paid plans, so the free tier will not accept a JKSV WebDAV connection. In return, the paid side is simple to reason about. pCloud sells both subscriptions and lifetime, one-time-payment plans, and that lifetime structure suits save archives particularly well, because your backup history is something you want to keep for years without a renewal deciding whether it survives. For most readers who want automatic uploads with the least ongoing thought, this is the default recommendation.
Koofr: WebDAV on Every Plan
Koofr’s distinguishing point is breadth: it includes WebDAV across its plans rather than reserving it for a higher tier, and it also offers lifetime-style deals through its sales partners from time to time. If you prefer a smaller European provider, or you find pCloud’s paid gate for WebDAV unappealing, Koofr is the natural second candidate for the same JKSV setup — the configuration on the console is the same idea, only the provider account changes.
Google Drive: The Free Native Route
If you already have a Google account with free space, JKSV’s built-in Google Drive connection is the zero-new-accounts option. There is no WebDAV address to configure and no extra subscription to evaluate; you sign in once and backups can sync to Drive. The trade-offs are structural rather than technical: your archive lives inside a general-purpose account alongside everything else, your free space is shared with mail and photos, and growing beyond it means joining Google’s own subscription ladder. For light libraries and first-time backup routines, though, it is the easiest place to start — and starting matters more than optimizing.
Self-Hosted: Nextcloud on Your Own Server
The fourth route removes the provider entirely. A self-hosted Nextcloud — on a small home server, or on an inexpensive hosted storage box from a company such as Hetzner — exposes WebDAV that JKSV can upload to, under storage you control. The cost structure is different rather than simply cheaper: a modest recurring server or storage fee, plus your own time for setup, updates, and security. Readers who already run a home server will find this the most satisfying option; readers who do not should count the maintenance honestly before choosing it to save money.
Choosing by Effort and Cost Structure
- Least effort overall: Google Drive, because JKSV connects natively and many readers already have an account.
- Least long-term attention: pCloud on a lifetime, one-time plan, because the WebDAV backup destination is settled in a single purchase decision.
- Most flexible provider choice: Koofr, because WebDAV is available across its plans.
- Most control: Self-hosted Nextcloud, at the price of ongoing maintenance that never fully disappears.
Whichever destination you choose, pair it with a local habit: keep the card copy, a PC copy moved with a reader from our guide to the best card readers and USB accessories, and the cloud copy, so no single failure can take all three. If you are still choosing the card those backups start on, see our guide to the best microSD cards for Switch save backups. The provider matters less than the pattern — automatic uploads, kept forever, on storage you understand.
This page contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you. See our Affiliate Disclosure.