JKSV’s WebDAV support means your cloud backup backend is a choice, not a default. Koofr, a self-hosted Nextcloud, a Hetzner Storage Box and Google Drive all work with JKSV, but they differ in how you connect, what WebDAV access depends on, and how much control you keep. This comparison sticks to how each option connects to JKSV and what to verify, so you can pick a backend that matches your priorities. You will need JKSV from the download page either way. More context is on the cloud backup hub.
Two connection models: native and WebDAV
Google Drive is the odd one out, in a good way: it is natively integrated into JKSV, signed in with the Limited Input flow described in our Google Drive setup guide, and needs no configuration file. Every other backend here connects over WebDAV through sd:/config/JKSV/webdav.json, following the steps in the WebDAV setup guide. Native is simpler; WebDAV is portable, because the same setup pattern works across providers and your own server.
All of them receive the same thing from JKSV: ZIP archives, since cloud backups are always ZIP. Provider choice therefore changes where your saves live and under whose rules, not the backup format itself.
Koofr: WebDAV on every plan
Koofr’s distinguishing point is that WebDAV support is included across its plans, including its lifetime option. For JKSV users that removes the plan-checking step that catches people out elsewhere. You create the backup folder in Koofr, note its WebDAV address and credentials, and fill in the same webdav.json fields as any other WebDAV backend. If you want to try it, you can sign up through our Koofr link; this site may earn a commission if you do, at no extra cost to you.
Koofr suits players who want a hosted service without running a server, and who like the idea of a lifetime plan for an archive they intend to keep for years. As with any host, verify a test upload and a test restore before trusting it with your only cloud copy.
Self-hosted: Nextcloud and Hetzner Storage Box
A self-hosted Nextcloud gives you WebDAV on hardware or a server you control, with no provider plan deciding whether the protocol is switched on. For JKSV it behaves like any other WebDAV endpoint: origin, basepath, username and password in webdav.json. A Hetzner Storage Box offers a similar WebDAV-accessible storage target without you maintaining the Nextcloud software itself. Both keep your save archive off the big platforms, which is the main reason players choose this route.
The trade-off is responsibility. You handle uptime, updates and the safety of the server itself, and a self-hosted box in the same house as the console does not protect against every disaster a remote host would. Many players pair a home server with one hosted copy for exactly that reason, as the cloud versus local strategy guide discusses.
pCloud and Google Drive, briefly
pCloud is covered in full in its own setup guide; the headline fact is that its WebDAV access has required a paid plan since February 2022, with the standard and European WebDAV addresses differing by account region. Google Drive needs no WebDAV at all thanks to the native integration, and for many players it is the fastest route to a working off-console backup, using an account they already have.
Neither is a wrong answer. pCloud offers lifetime plans for those who dislike subscriptions, and Drive offers zero-friction setup. The question is which set of rules and whose infrastructure you want your archive under.
How to choose
Choose Google Drive for the simplest setup. Choose Koofr for hosted WebDAV without a plan restriction on the protocol. Choose pCloud if its lifetime option appeals and you accept the paid-plan requirement for WebDAV. Choose Nextcloud or a Storage Box if control matters most and you are willing to maintain it. Whichever you pick, enable auto-upload, keep local backups on, and test a restore.
Backends can also change later. Because JKSV exports standard ZIPs, moving your archive between providers is a file copy, not a conversion, so today’s choice does not trap tomorrow’s saves.