
      <h2>First: sync is a membership feature</h2>
      <p>Without a membership each device works on its own and nothing syncs automatically. That is not a fault.</p>
      <p>One point worth stating plainly: <strong>using your own WebDAV server also requires a membership.</strong> What membership buys is the ability to sync across devices; where the data lives is your choice. Your own server simply has no size limit.</p>

      <h2>Setting it up</h2>
      <p>The first three steps are the same whichever storage you pick:</p>
      <ol>
        <li><strong>Sign in</strong> (both devices must use the same account)</li>
        <li><strong>Subscribe</strong></li>
        <li>Go to <strong>Me → Data management → Backup</strong></li>
      </ol>
      <figure class="help-figure help-figure-portrait">
        <img src="/screenshoots/help/data-mgmt.png" alt="Data management screen: export, import and cloud backup" loading="lazy" />
        <figcaption>Sync lives under Backup, alongside import and export</figcaption>
      </figure>
      <p><strong>You have to pick a sync method yourself</strong> — two options appear: our servers, or your own WebDAV. <strong>Neither is preselected</strong>, and nothing syncs until you choose. Each is covered below.</p>

      <h3>Option 1: hosted</h3>
      <p>Tap <strong>Use KeyMe Pass server</strong> in that chooser. There is <strong>nothing to fill in</strong> — it configures itself.</p>
      <p>Then sign in to the same account on your second device and let it sync down.</p>

      <h3>Option 2: your own WebDAV</h3>
      <p>Tap <strong>Custom WebDAV server</strong> in the same chooser and a form appears with <strong>four fields</strong>:</p>
      <figure class="help-figure help-figure-portrait">
        <img src="/screenshoots/help/webdav-config.png" alt="The WebDAV server form: server URL, username, password and storage path fields above a Save and start syncing button" loading="lazy" />
        <figcaption>The WebDAV form; storage path defaults to /keyme</figcaption>
      </figure>
      <table>
        <thead><tr><th>Field</th><th>What to enter</th></tr></thead>
        <tbody>
          <tr><td><strong>Server URL</strong></td><td>Your WebDAV address; must start with <code>http://</code> or <code>https://</code></td></tr>
          <tr><td><strong>Username</strong></td><td>Your login name for that service</td></tr>
          <tr><td><strong>Password</strong></td><td>⚠️ Not necessarily your login password — see below</td></tr>
          <tr><td><strong>Storage path</strong></td><td>Optional; defaults to <code>/keyme</code>. Data is stored under this directory</td></tr>
        </tbody>
      </table>
      <p>Tap <strong>Save and start syncing</strong>. This <strong>actually connects to the server to verify</strong> rather than just saving the values, so a wrong address or password fails immediately instead of at the first sync.</p>
      <p>Verification can take tens of seconds depending on the server — <strong>do not close the sheet while it runs</strong>.</p>

      <h4>⚠️ The password field: many services want an app password</h4>
      <p>This is the most common reason setup fails. <strong>Many storage providers do not let third-party apps use your account password</strong>; you generate a separate one instead.</p>
      <ul>
        <li><strong>Nextcloud / ownCloud</strong> — your login password usually works, but if two-factor authentication is on you <strong>must</strong> use an app password (Personal settings → Security). The WebDAV URL typically looks like <code>https://your-domain/remote.php/dav/files/username/</code>; check what your server displays.</li>
        <li><strong>Synology</strong> — install and enable WebDAV Server from Package Center; use the address and port it shows.</li>
        <li><strong>Nutstore (Jianguoyun)</strong> — an app password is required. Generate one under Account info → Security → Third-party app management on their website; the server address is shown on the same page.</li>
      </ul>
      <p>If you get a 404 or 405 after saving, that is a different problem (a non-standard protocol implementation on the server side) — see <a href="/help/webdav">Custom WebDAV sync returns 404/405</a>.</p>

      <h3>Last step</h3>
      <p>Either way, finish the same: <strong>sign in to the same account on your second device</strong> and let it sync down.</p>
      <p>Once configured, a sync card appears on the home screen showing the last sync time, with a Sync now button for manual runs.</p>

      <h2>Hosted or your own server</h2>
      <table>
        <thead><tr><th></th><th>Hosted</th><th>Your own WebDAV</th></tr></thead>
        <tbody>
          <tr><td>Setup</td><td>Just pick it</td><td>Server address, username, password</td></tr>
          <tr><td>Capacity</td><td>1 GB with membership</td><td><strong>No limit</strong> (whatever your server has)</td></tr>
          <tr><td>Where data sits</td><td>Our servers</td><td>Yours</td></tr>
          <tr><td>Good for</td><td>Not wanting to fiddle</td><td>Deciding exactly where data lives</td></tr>
        </tbody>
      </table>
      <p>The encryption is identical either way: <strong>data is encrypted on your device before upload</strong>, and the server holds ciphertext. Choosing your own server is not about being "more secure" — it is about controlling capacity and location.</p>

      <h2>The first sync</h2>
      <p>The first run uploads the whole vault, which takes a while with many entries or large attachments.</p>
      <p>During first-time setup, sync waits about 15 seconds and then <strong>continues in the background</strong> rather than blocking the app.</p>
      <p><strong>The vault may look empty at that point while data is still arriving.</strong> The sync card on the home screen shows progress — give it a moment rather than force-quitting the app.</p>
      <p>If the system kills it midway, the next unlock picks up where it left off.</p>
      <p>Worth doing the first sync on Wi-Fi, with the app in the foreground for a moment.</p>

      <h2>After that</h2>
      <p>⚠️ <strong>Automatic sync is off by default</strong> and has to be switched on in the backup page. While it is off, syncing happens only when you tap "Sync now".</p>
      <p>Once on, you can choose an interval: <strong>1 / 3 / 7 / 14 / 30 days</strong>.</p>
      <p>Two things to know:</p>
      <ul>
        <li><strong>It only checks while the app is unlocked</strong> — nothing syncs quietly in the background while locked</li>
        <li><strong>It is not a live push.</strong> Device A uploads, then device B pulls</li>
      </ul>
      <p>So to see a change on the other device straight away, tap "Sync now" on both.</p>

      <h2>If the same entry changes on two devices</h2>
      <p><strong>Fields are resolved separately, so edits to different fields do not overwrite each other</strong> — change a note on your phone and the password on your desktop, and both survive. Only when the <strong>same field</strong> changed on both sides does the later edit win. See <a href="/help/sync-troubleshooting">When sync fails</a>.</p>

      <h2>The browser extension</h2>
      <p>The extension syncs <strong>passwords, two-factor codes and passkeys</strong>. Documents, payment cards, secure notes and SSH keys stay in the app.</p>

      <h2>Related</h2>
      <ul>
        <li><a href="/help/sync-troubleshooting">When sync fails</a></li>
        <li><a href="/help/webdav">WebDAV 404/405 errors</a></li>
        <li><a href="/help/export-backup">Export and backup</a></li>
      </ul>
    

How to Configure Multi-Device Sync: Hosted or Your Own WebDAV


        <h2>Why 404 / 405 happens</h2>
        <p>Syncing starts by checking whether a file already exists on the server. The WebDAV spec says a HEAD request answers that, but <strong>plenty of servers implement HEAD loosely</strong> — the file is there, yet the response is 404 or 405, and the sync stops.</p>
        <p>This is a difference in protocol implementation. It does <strong>not</strong> mean you filled something in wrong, and it does not mean your data is damaged.</p>

        <h2>The compatibility handling is already on</h2>
        <p>For custom WebDAV servers, KeyMe Pass <strong>defaults to the more forgiving checks</strong>:</p>
        <ul>
          <li><strong>No HEAD requests</strong> — existence is checked with GET instead</li>
          <li><strong>Directories and large files (including attachments) are checked with PROPFIND</strong></li>
        </ul>
        <p>There is <strong>nothing to switch on, and no way to switch it off</strong>. Earlier versions offered a "standard / enhanced" choice in settings; that option has since been <strong>removed and the enhanced behaviour made unconditional</strong>. If an older guide tells you to enable it, the toggle simply is not there any more — that is expected.</p>

        <h2>If it still fails</h2>
        <p>Work through these in order:</p>
        <ol>
          <li><strong>Is the URL the WebDAV endpoint?</strong> It is often not the same address as the service's web interface.</li>
          <li><strong>Are the credentials the right ones?</strong> Several services require a <strong>separately generated app password</strong> rather than your normal sign-in password.</li>
          <li><strong>Does the storage path exist?</strong> The default is <code>/keyme</code>. Some servers will not create it for you — make the folder first.</li>
          <li><strong>Can that folder be written to?</strong> Read-only access connects fine but cannot upload.</li>
          <li><strong>Does the server support PROPFIND?</strong> It is a basic WebDAV method; a few stripped-down servers disable it, and no client-side setting can work around that.</li>
        </ol>
        <p>If switching to <a href="/help/sync-setup">the hosted storage</a> syncs normally, the problem is almost certainly on the self-hosted side.</p>

        <h2>Your data stays protected either way</h2>
        <p>Whichever server you use, and whether or not the sync completes, <strong>data is encrypted on your device before it is uploaded</strong> — the server only ever holds ciphertext. These errors affect whether syncing finishes, never whether content reaches the server in the clear. See <a href="/security">the security page</a>.</p>

        <h2>Related</h2>
        <ul>
          <li><a href="/help/sync-setup">Setting up multi-device sync</a></li>
          <li><a href="/help/sync-troubleshooting">When sync fails</a></li>
        </ul>
    

Fixing Custom WebDAV Sync Errors (404/405)


      <h2>Two different things</h2>
      <table>
        <thead><tr><th></th><th>Export file</th><th>Cloud backup / sync</th></tr></thead>
        <tbody>
          <tr><td>Result</td><td>A file you keep yourself</td><td>Data in the cloud, shared across devices</td></tr>
          <tr><td>Triggered by</td><td>You, manually</td><td>Automatically</td></tr>
          <tr><td>Cost</td><td><strong>Free, unlimited</strong></td><td>Membership feature</td></tr>
          <tr><td>Good for</td><td>Archiving, moving to other software, a quick look</td><td>Everyday multi-device use</td></tr>
        </tbody>
      </table>
      <p>Both live under My → Data management.</p>

      <h2>Export: which format</h2>
      <table>
        <thead><tr><th></th><th>ZIP (recommended)</th><th>CSV</th></tr></thead>
        <tbody>
          <tr><td>Contains</td><td>Everything: passwords, MFA, payment cards, ID documents (with images), secure notes, tags, folders, field templates</td><td>Logins only: passwords, MFA, secure notes</td></tr>
          <tr><td>Encryption</td><td><strong>Supported</strong></td><td><strong>Not supported</strong> (plain text)</td></tr>
          <tr><td>Good for</td><td>Full backup, changing devices</td><td>Moving to other software, a quick look</td></tr>
        </tbody>
      </table>
      <p><strong>For a backup, choose ZIP and turn encryption on.</strong> CSV is a plain-text table — anyone who can open it sees every password. Use it only when something genuinely requires CSV, and delete it afterwards.</p>

      <figure class="help-figure help-figure-portrait">
        <img src="/screenshoots/help/export.png" alt="Export screen: format picker, the note that passkeys are excluded, and the encryption toggle" loading="lazy" />
        <figcaption>The export screen spells out what the chosen format includes (screenshot shows the Chinese interface)</figcaption>
      </figure>

      <h3>⚠️ Passkeys are not in the export</h3>
      <p>Passkeys are excluded from every export format. They are protected by encrypted cloud sync instead, and <strong>come back automatically once you sign in on a new device</strong>.</p>
      <p>So: <strong>an export file is not all of your data.</strong> If you migrate by file alone, without sync, passkeys do not travel with it.</p>

      <h3>The encryption password</h3>
      <p>At least 6 characters. It is <strong>separate from your master password</strong> and must be remembered on its own — importing asks for it, and without it the file cannot be opened.</p>

      <h2>Importing it back</h2>
      <p>My → Data management → Import, choose KeyMe Pass as the source, then pick the file. ZIP, CSV and JSON files from older versions all work.</p>
      <p>An encrypted ZIP asks for the password you set at export time.</p>

      <h2>Moving to a new phone</h2>
      <h3>With membership (sync on)</h3>
      <p>Sign in to the same account on the new device and let sync finish. Worth running a manual sync on the old device first.</p>

      <h3>Without membership</h3>
      <ol>
        <li>Old device: export a ZIP (encrypted is advisable)</li>
        <li>Transfer the file</li>
        <li>New device: Data management → Import → KeyMe Pass → pick the file</li>
      </ol>
      <p>Remember that passkeys do not travel in the file (above).</p>

      <h2>How often to back up</h2>
      <p>There is no rule. A reasonable habit: <strong>with sync on you do not need frequent manual exports</strong>, but one is worth keeping at these moments —</p>
      <ul>
        <li>Before changing phones</li>
        <li>Before changing your master password</li>
        <li>After the first proper tidy-up of your vault</li>
      </ul>

      <h2>Related</h2>
      <ul>
        <li><a href="/help/import">Supported import sources and formats</a></li>
        <li><a href="/help/sync-setup">Setting up multi-device sync</a></li>
      </ul>
    

Export and Backup


      <h2>Which route applies to you</h2>
      <table>
        <thead><tr><th></th><th>Sync on (membership)</th><th>No sync</th></tr></thead>
        <tbody>
          <tr><td>How</td><td>Sign in on the new phone; everything returns</td><td>Export on the old phone, import on the new one</td></tr>
          <tr><td>Passkeys</td><td><strong>Come across</strong></td><td><strong>Do not</strong> (see below)</td></tr>
          <tr><td>Attachments, ID photos</td><td>Come across</td><td>Only if they had finished downloading</td></tr>
          <tr><td>What you do</td><td>Enter the master password once</td><td>Export, transfer the file, import</td></tr>
        </tbody>
      </table>
      <p>If you have a membership and sync is already on, <strong>go straight to the next section — no export needed</strong>.</p>

      <h2>Route 1: sign in and it comes back (recommended)</h2>
      <ol>
        <li>Install KeyMe Pass on the new phone</li>
        <li>Choose "I already have an account" and enter your email</li>
        <li><strong>Enter your master password</strong></li>
        <li>Wait for the first sync</li>
      </ol>
      <p>That is all. <strong>You do not need the recovery key on the new phone</strong> — it exists for when you have forgotten the master password, not for moving devices, and it is restored to the new device automatically after you sign in.</p>
      <p>Nor is there anything to prepare on the old phone.</p>

      <h3>⚠️ An empty vault right after signing in is normal</h3>
      <p>The first sync pulls down the whole vault, which takes a while with many entries or large attachments. <strong>The app waits about 15 seconds and then lets you in</strong>, continuing in the background.</p>
      <p>What you see at that point may be empty or partial. <strong>That is expected.</strong> The sync card on the home screen shows progress; give it a moment.</p>
      <p>If the system kills it midway, the next unlock picks up where it left off. Worth doing the first sync on Wi-Fi with the app in the foreground.</p>

      <h2>Route 2: move a file</h2>
      <p>For when sync is off. Full steps are in <a href="/help/export-backup">Export and backup</a>; here is what matters when switching phones:</p>
      <ul>
        <li><strong>Choose ZIP, not CSV.</strong> CSV holds only passwords, codes and secure notes — documents, payment cards, SSH keys and attachments are all absent.</li>
        <li><strong>Turn encryption on.</strong> In an unencrypted ZIP, passwords and SSH private keys sit in plain text for anyone who gets the file.</li>
        <li>The encryption password is separate from your master password; remember it, because the import needs it.</li>
      </ul>

      <h3>⚠️ Passkeys do not travel this way</h3>
      <p><strong>Passkeys are not in any export format.</strong> Their only cross-device route is account sync.</p>
      <p>If you use passkeys and do not want sync, they will not appear on the new phone.</p>

      <h2>Three things that catch people out</h2>

      <h3>1. Exporting right after signing in loses attachments</h3>
      <p>Attachments and ID photos download separately during sync. <strong>Export before they finish and those files are missing from the package</strong> — the records are there, but the images will not open.</p>
      <p>To make a backup on the new phone, wait until sync has completed.</p>

      <h3>2. There is no remote wipe for the old phone</h3>
      <p>KeyMe Pass has <strong>no "sign out other devices" and no remote erase</strong>. After you switch, the data on the old phone is still there and still syncing.</p>
      <p>Clearing it is something you do on that device: sign out, or wipe local data under My → Security settings. Do this before selling or giving the phone away.</p>

      <h3>3. Leaving the old device on an old version causes damage</h3>
      <p>If you keep using the old phone, <strong>update it too</strong>.</p>
      <p>An older app does not recognise fields added in newer versions, and writes records back without them — <strong>wiping data that exists on your new device</strong>. The app warns about this before syncing.</p>

      <h2>One thing worth doing first</h2>
      <p><strong>Check you still have your recovery key.</strong> Switching phones does not need it, but if the master password will not come back to you on the new phone, the recovery key is the only thing that saves your data — without it the only way forward is an email reset, <strong>which erases everything in the cloud and on your devices</strong>.</p>
      <p>See <a href="/help/recovery-key">What the recovery key is, and what happens if you lose it</a>.</p>

      <h2>Related</h2>
      <ul>
        <li><a href="/help/sync-setup">Setting up multi-device sync</a></li>
        <li><a href="/help/export-backup">Export and backup</a></li>
        <li><a href="/help/recovery-key">What the recovery key is</a></li>
        <li><a href="/help/sync-troubleshooting">When sync fails</a></li>
      </ul>
    