JKSV cloud backup guides: WebDAV, Google Drive, auto-upload and remote save storage.
Every JKSV user eventually asks the same question: should save backups live on the SD card, in the cloud, or both? The honest answer is both, but for different jobs. Local copies restore instantly and work offline; cloud copies survive the failures that take the card or the console with them. This guide explains how…
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…
pCloud is a natural backend for JKSV because it speaks WebDAV, the same protocol JKSV uses to upload save backups to remote storage. Point JKSV at pCloud once, and your Switch saves can leave the console automatically after every backup. This guide covers the practical setup, the pCloud addresses to use, and one important plan…
Manual uploads only protect you on the days you remember to do them. JKSV can upload backups automatically, so every new backup is copied to your cloud destination as part of the backup itself. This guide explains how automatic upload behaves, the ZIP requirement behind it, and the local-copy option you should keep enabled. You…
JKSV includes a native Google Drive integration, so your Switch save backups can be uploaded to your own Drive account without running a separate server. The sign-in uses Google’s Limited Input flow, designed for devices like a console that have no comfortable way to complete a full browser login. This guide explains each step and…
WebDAV is the most flexible way to send JKSV backups off your console. Instead of relying on one built-in service, JKSV can upload save backups to any WebDAV server you control or subscribe to, from a home NAS to a hosted storage account. This guide walks through the complete webdav.json configuration, step by step. If…
