
        <h2>What is Autofill</h2>
        <p>KeyMe Pass <strong>Autofill</strong> can <strong>fill and save</strong> account passwords in third-party apps and browsers (non-membership capability). Please complete the <strong>default autofill service</strong> and <strong>permissions</strong> as guided in the app and on this page.</p>
        <p>Platform support at a glance:</p>
        <ul>
          <li><strong>Android</strong>: password fill and save, plus passkeys (requires Android 14 or later — see below).</li>
          <li><strong>iOS</strong>: password fill and passkeys (iOS 17+); <strong>auto-saving new passwords requires iOS 26.2 or later</strong>.</li>
          <li><strong>macOS</strong>: password fill and passkeys (macOS 14+), <strong>Safari and native apps only</strong>, and <strong>saving new passwords is not supported</strong>.</li>
          <li><strong>HarmonyOS Next</strong>: system autofill is not supported yet (the OS has not exposed the APIs).</li>
        </ul>

        <h2>Before you start</h2>
        <ol>
          <li>Turn on the Autofill switch in KeyMe Pass first.</li>
          <li>Set KeyMe Pass as the <strong>default autofill service</strong> in <strong>system settings</strong>, or suggestions will not appear in other apps.</li>
          <li>Complete the background pop-up and notification permissions as prompted by your device.</li>
        </ol>
        <p>If the app cannot open Settings, go there manually, search for &quot;Autofill&quot; or &quot;Default apps&quot;, and set KeyMe Pass as the default autofill provider.</p>

        <h2>Android: recommended steps</h2>
        <h3>Mode A: Standard Autofill (recommended first)</h3>
        <p>This is the primary path for most apps that support standard Android Autofill APIs.</p>
        <h4>1. Default autofill service</h4>
        <p>First, in system settings, search for Autofill and set KeyMe Pass as the <strong>default autofill service</strong>. Only after this can you use filling in other apps.</p>

        <h4>2. Enable Autofill</h4>
        <p>Then return to KeyMe Pass Autofill settings and turn on the main switch.</p>

        <h4>3. Permission hints (as needed)</h4>
        <p>Follow in-app prompts (names may vary by device):</p>
        <ul>
          <li><strong>Background pop-up (strongly recommended on Chinese Android systems)</strong>: without it, tapping to fill may do nothing. Names vary by system; searching settings for 后台弹窗 / 后台弹出 / 后台启动 is quickest — see <a href="/help/autofill-troubleshooting">troubleshooting autofill</a>.</li>
          <li><strong>Notifications (highly recommended)</strong>: helps with password-update flows (behavior varies by Android version).</li>
        </ul>
        <div class="autofill-media-grid">
          <div class="autofill-media-item">
            <img src="/screenshoots/help/autofill-settings.png" alt="The in-app Autofill settings screen: default fill service, background pop-up, notifications and accessibility" />
            <p class="autofill-media-caption">The in-app Autofill settings screen, showing each permission's state</p>
          </div>
        </div>
        <p>After returning from system settings, use <strong>refresh status</strong> in the app to update detection.</p>

        <h3 id="android-accessibility">Mode B: Accessibility recognition (Android enhanced detection)</h3>
        <p>For some apps that do not trigger the standard Android Autofill APIs, you can enable <strong>Accessibility recognition</strong> as a supplemental detection path.</p>
        <ol>
          <li>
            In the Autofill settings page, first turn on &quot;Accessibility recognition&quot;, then turn on &quot;Smart floating window&quot; that appears beneath it (the floating window is a sub-option and only appears once accessibility recognition is enabled).
            <div class="autofill-step-media">
              <img src="/screenshoots/help/autofill-settings.png" alt="With accessibility recognition on, the smart popup and overlay permission rows appear below it" />
              <p class="autofill-media-caption">Step 1: Enable Accessibility recognition and smart floating window</p>
            </div>
          </li>
          <li>
            Open the system Accessibility settings homepage.
            <div class="autofill-step-media">
              <img src="/screenshoots/help/a11y-home.png" alt="The system accessibility settings screen with KeyMe Pass switched on" />
              <p class="autofill-media-caption">Step 2: Open system Accessibility settings</p>
            </div>
          </li>
          <li>
            Enable the KeyMe Pass accessibility service permission.
            <div class="autofill-step-media">
              <img src="/screenshoots/help/a11y-service.png" alt="Turning on the KeyMe Pass accessibility service in system settings" />
              <p class="autofill-media-caption">Step 3: Enable KeyMe Pass accessibility service</p>
            </div>
          </li>
          <li>
            Optional: trigger accessibility recognition from the quick-settings tile.
            <div class="autofill-step-media">
              <img class="is-landscape" src="/screenshoots/help/quick-tile.png" alt="The KeyMe Pass fill tile under Apps in the quick-settings editor" />
              <p class="autofill-media-caption">Step 4: Trigger from quick-settings tile</p>
            </div>
          </li>
        </ol>
        <p class="autofill-media-note">Usage flow can be viewed in this video:</p>
        <video class="autofill-media-video" controls preload="metadata">
          <source src="/screenshoots/autofill/accessibility-fullflow.mp4" type="video/mp4" />
          Your browser does not support video playback.
        </video>

        <h3 id="android-browser-save">Save prompts in browsers</h3>
        <p>In browsers such as <strong>Edge</strong>, KeyMe Pass <strong>fills passwords normally</strong> but does <strong>not</strong> show a "save / update password" prompt. This is a deliberate trade-off, for the reason below.</p>
        <p>Android serves these browsers through a <strong>compatibility mode</strong> channel. In that mode, the password content the system hands to a password manager is <strong>the dots shown on screen (••••••), not the real password</strong> — this is how Android works, and every third-party password manager receives the same thing. That causes two problems:</p>
        <ul>
          <li><strong>The wrong value gets saved</strong>: a string of dots would be stored as your password, potentially overwriting a correct entry and breaking your next sign-in.</li>
          <li><strong>You get asked every time</strong>: the system cannot tell whether this password matches the stored one, so it asks again on every sign-in.</li>
        </ul>
        <p>So in compatibility mode we <strong>no longer show the save prompt</strong>, ensuring your passwords are <strong>never overwritten with invalid content</strong>. <strong>Filling is completely unaffected.</strong></p>
        <p>To add a new password for such a browser, please <strong>add it manually in KeyMe Pass</strong>, or switch to a browser with <strong>native integration</strong> (see below).</p>

        <h4>Chrome: enable native integration (recommended)</h4>
        <p>Chrome moved to the native integration channel in <strong>version 137</strong>, which is not affected by the compatibility-mode limitation above — <strong>save prompts work normally</strong> there. To enable it:</p>
        <ol>
          <li>Make sure KeyMe Pass is set as the <strong>default autofill service</strong> in system settings.</li>
          <li>Open Chrome and go to <strong>Settings → Autofill and passwords</strong>.</li>
          <li>Choose <strong>&quot;Autofill using another service&quot;</strong> and point it at KeyMe Pass.</li>
        </ol>
        <p class="note">Note: whether a browser uses compatibility mode or native integration is decided by the system and the browser version; KeyMe Pass cannot switch it for you. Edge, Samsung Internet, Opera, Vivaldi and most China-market browsers still use compatibility mode today.</p>

        <h2>iOS: recommended steps</h2>
        <p>Open <strong>Settings → General → AutoFill &amp; Passwords → AutoFill from</strong> and enable KeyMe Pass (exact labels depend on iOS language and version).</p>
        <p>Some apps may show <strong>no candidates</strong> — it depends on whether the app exposes fillable fields to the system.</p>

        <h3>About saving new passwords (requires iOS 26.2 or later)</h3>
        <p>Handing a new password to a third-party password manager requires a system API for it. Apple <strong>only introduced that API in iOS 26.2</strong>; on earlier versions the system simply never notifies third-party password managers that there is a new password to save. This is a system-level limitation and applies to every password manager equally.</p>
        <p>So:</p>
        <ul>
          <li><strong>iOS 26.2 and later</strong>: new passwords can be saved automatically; you will be prompted after signing up or signing in.</li>
          <li><strong>Below iOS 26.2</strong>: no save prompt appears. Please <strong>add entries manually</strong> in KeyMe Pass, or <strong>add directly from the password suggestion list</strong>; newly added items are automatically associated and stored.</li>
        </ul>

        <h3>Fill from the long-press menu (iOS 18 and later)</h3>
        <p>On iOS 18 and later, even if a field is not recognised as a login field, you can <strong>long-press the text field</strong> and choose AutoFill from the menu to pick content from KeyMe Pass. This helps with custom sign-in screens.</p>

        <h2>macOS: recommended steps</h2>
        <p>Open <strong>System Settings → General → AutoFill &amp; Passwords</strong> and enable KeyMe Pass. Once enabled, you can fill passwords and passkeys in Safari and in native apps that support AutoFill.</p>

        <h3>Important limitations</h3>
        <p>Two system-level macOS limitations to know about — neither is a KeyMe Pass fault:</p>
        <ul>
          <li>
            <strong>Safari and native apps only.</strong> The macOS system AutoFill pipeline is open only to Safari and native apps; <strong>Chrome, Edge, Firefox and other browsers do not integrate with it</strong>, so KeyMe Pass suggestions will not appear there — this applies to every third-party password manager. For those browsers, use the <strong>KeyMe Pass browser extension</strong> instead.
          </li>
          <li>
            <strong>New passwords cannot be saved.</strong> macOS provides no API for handing a new password back to a third-party password manager, so <strong>no save prompt appears</strong>. Please <strong>add new passwords manually</strong> in the KeyMe Pass app; once added, they fill normally in Safari and native apps.
          </li>
        </ul>
        <p class="note">macOS autofill requires macOS 14 or later.</p>

        <h2>Other notes</h2>
        <h3>If matching fails: check the entry's URL and app linking</h3>
        <ul>
          <li><strong>Web (domain matching)</strong>: the login URL participates in matching; for WebView or multi-domain sites, add or verify domains on the password entry.</li>
          <li><strong>Android native apps</strong>: package name and related metadata matter; in some cases you can use <code>androidapp://package.name</code> in the URL field (replace with the real package name) to associate the entry with an app.</li>
        </ul>
        <p>If it still fails, check that the URL and app association fields on the entry are correct.</p>

        <h3>Known limitations at a glance</h3>
        <ul>
          <li>Some apps (e.g. certain messengers) <strong>do not use the standard system autofill APIs</strong> and may never show candidates.</li>
          <li>Browsers, in-app WebViews, and redirects can make <strong>domain matching less stable</strong>.</li>
          <li><strong>Android</strong>: some browsers (compatibility mode) <strong>do not prompt to save passwords</strong>; filling is unaffected.</li>
          <li><strong>iOS</strong>: versions <strong>below 26.2 cannot save new passwords automatically</strong>; add them manually.</li>
          <li><strong>macOS</strong>: system autofill works <strong>only in Safari and native apps</strong> — use the browser extension elsewhere — and <strong>cannot save new passwords</strong>.</li>
          <li><strong>HarmonyOS Next</strong> (HarmonyOS 5.x and above) currently <strong>does not support autofill</strong> because the system has not exposed the required APIs. HarmonyOS versions below 5.x are Android-compatible and can use the Android autofill capability.</li>
        </ul>

        <h2>Passkeys</h2>
        <p>Beyond passwords, KeyMe Pass can also store and use <strong>passkeys</strong> for passwordless sign-in on supported sites and apps. For setup, OS version requirements and device compatibility, see the <a href="/help/passkey">Passkey Guide</a>.</p>
        <p>For everything else KeyMe Pass does beyond autofill, see <a href="/features">the features page</a>.</p>
      

Autofill Guide


        <h2>What the extension does</h2>
        <p>The KeyMe Pass browser extension works on <strong>Chrome, Edge and other Chromium-based browsers</strong> and provides:</p>
        <ul>
          <li><strong>Autofill</strong>: detects login fields and fills saved credentials with one click.</li>
          <li><strong>Save passwords</strong>: prompts to save new credentials to KeyMe Pass when you sign in or register.</li>
          <li><strong>Generate strong passwords</strong>: create and fill a high-strength password on sign-up / change-password pages.</li>
          <li><strong>2FA codes</strong>: manage TOTP codes and fill them quickly at login.</li>
          <li><strong>Cross-device sync</strong>: shares the same encrypted vault as the mobile app (sync required).</li>
        </ul>
        <p>The extension is <strong>end-to-end encrypted</strong> — your master password and vault are decrypted only locally, same as the app.</p>

        <h2>How to install</h2>
        <h3>Option 1: Install from the official store (recommended)</h3>
        <p>One-click install with automatic updates:</p>
        <ul>
          <li><strong>Chrome</strong>: <a href="https://chromewebstore.google.com/detail/glpaaajmfbcidfjghfkeikmohajfchig" target="_blank" rel="noopener noreferrer">Chrome Web Store</a></li>
          <li><strong>Edge</strong>: <a href="https://microsoftedge.microsoft.com/addons/detail/cpafojcokbbpfomgdhfkjojeboagicho" target="_blank" rel="noopener noreferrer">Microsoft Edge Add-ons</a></li>
        </ul>
        <p>Brave, Arc and other Chromium browsers can install from the Chrome Web Store.</p>
        <figure class="help-figure">
          <img src="/screenshoots/help/store-chrome.png" alt="The KeyMe Pass listing in the Chrome Web Store, published by keymepass.com" loading="lazy" />
          <figcaption>Chrome Web Store: the publisher should read <strong>keymepass.com</strong> with the blue verified badge (screenshot shows the Chinese interface)</figcaption>
        </figure>
        <figure class="help-figure">
          <img src="/screenshoots/help/store-edge.png" alt="The KeyMe Pass listing in the Microsoft Edge Add-ons store, developed by KeyMe Pass Team" loading="lazy" />
          <figcaption>Edge Add-ons: the developer should read <strong>KeyMe Pass Team</strong> (screenshot shows the Chinese interface)</figcaption>
        </figure>

        <h3>Option 2: Download the zip and load unpacked</h3>
        <p>For when you can't reach the stores. Installs this way don't update automatically.</p>
        <ol>
          <li>On the <a href="/download">download page</a>, click "Manual Install" on the browser extension card to get the zip.</li>
          <li>Unzip it into a <strong>permanent folder</strong> (don't delete the folder — the extension runs from it).</li>
          <li>Open <code>chrome://extensions</code> in your browser (<code>edge://extensions</code> on Edge).</li>
          <li>Turn on <strong>Developer mode</strong> in the top-right corner.</li>
          <li>Click <strong>Load unpacked</strong> and select the folder from step 2.</li>
          <li>The KeyMe Pass icon appears in the toolbar. Pin it via the puzzle-piece menu for quick access.</li>
        </ol>
        <p>Tip: to update, download the new zip, overwrite the same folder, then click the extension's <strong>reload</strong> button on the extensions page.</p>

        <h2>Getting started</h2>
        <ol>
          <li>Click the KeyMe Pass toolbar icon and <strong>unlock</strong> your vault with your master password.</li>
          <li>On any login page, a small KeyMe Pass icon appears next to the username/password field — click it to pick and fill a saved account.</li>
          <li>After signing in to a new site, the extension offers to <strong>save</strong> that credential to your vault.</li>
          <li>On sign-up or change-password pages, choose <strong>Generate strong password</strong> in the password field.</li>
        </ol>
        <p>If the icon covers a site's built-in "show password" button, just <strong>drag</strong> it aside.</p>

        <h2>FAQ</h2>
        <ul>
          <li><strong>Which browsers are supported?</strong> Chrome, Edge and other Chromium-based browsers. Firefox and Safari are not supported yet.</li>
          <li><strong>No autofill icon?</strong> Make sure the extension is unlocked. Some sites render password fields lazily — refresh the page or click into the field and try again.</li>
          <li><strong>Is my data safe?</strong> The extension is end-to-end encrypted like the app; we cannot read your master password or vault.</li>
        </ul>
    

Browser Extension Guide


        <h2>What is a passkey</h2>
        <p>A <strong>passkey</strong> is a modern replacement for passwords. Instead of typing a password, you sign in by confirming your identity with your <strong>fingerprint, face, or device passcode</strong>.</p>
        <p>Compared with passwords, passkeys have several fundamental advantages:</p>
        <ul>
          <li><strong>Phishing-resistant</strong>: a passkey is bound to the site's domain and simply will not be offered on a lookalike site.</li>
          <li><strong>Unaffected by site breaches</strong>: the site only stores a public key; the private key stays on your device and in KeyMe Pass, so a leaked public key is useless to an attacker.</li>
          <li><strong>Nothing to remember</strong>: there is no password to guess, reuse, or write on a sticky note.</li>
        </ul>
        <p>KeyMe Pass can act as your <strong>passkey manager</strong>: passkeys you create are stored in KeyMe Pass and synced to your other devices with end-to-end encryption.</p>

        <h2>Before you start</h2>
        <ol>
          <li>Set KeyMe Pass as the <strong>default autofill service</strong> in system settings (on Android, also enable it under "Passkeys, passwords and data services"). See the <a href="/help/autofill">Autofill Guide</a> for setup steps.</li>
          <li>Make sure your device has a <strong>screen lock</strong> (fingerprint, face, or PIN/passcode) — the system requires one before passkeys can be used.</li>
          <li>Check that your OS version meets the <strong>device and OS requirements</strong> below.</li>
        </ol>

        <h2>Device and OS requirements</h2>
        <p>Passkeys rely on newer system capabilities. Requirements per platform:</p>
        <ul>
          <li><strong>Android</strong>: <strong>Android 14 or later</strong>, and the system must include the <strong>Credential Manager</strong> framework.</li>
          <li><strong>iOS / iPadOS</strong>: <strong>iOS 17 or later</strong>.</li>
          <li><strong>macOS</strong>: <strong>macOS 14 or later</strong>, and <strong>only in Safari and native apps</strong> (Chrome, Edge and Firefox do not integrate with the macOS system pipeline).</li>
          <li><strong>HarmonyOS Next</strong>: signing in with passkeys is <strong>not supported yet</strong> (the OS has not exposed the required APIs).</li>
        </ul>

        <h3 id="android-compatibility">Android device compatibility (important)</h3>
        <p>Even on Android 14 or later, <strong>some devices still cannot use passkeys</strong>. Passkeys depend on Google's <strong>Credential Manager</strong> framework, which is not present on every Android device:</p>
        <ul>
          <li><strong>Huawei devices with HMS only</strong> (no Google Mobile Services) <strong>cannot use</strong> passkeys.</li>
          <li><strong>Some China-market ROMs</strong> ship a reduced version of the framework or omit the selection UI, so passkeys may be <strong>unavailable or behave unexpectedly</strong>.</li>
          <li>International models, Pixel devices, and most devices with Google services work normally.</li>
        </ul>
        <p>KeyMe Pass detects whether your device is supported. <strong>If it is not, the passkey page in the app shows a notice banner</strong> and the feature is unavailable — this is a device and OS limitation, not a KeyMe Pass fault.</p>
        <p class="note">On unsupported devices you can still <strong>view and manage</strong> passkeys synced from your other devices; you just cannot sign in with them.</p>

        <h2>Creating a passkey</h2>
        <p>On a site or app that supports passkeys:</p>
        <ol>
          <li>Go to your account's <strong>security settings</strong> and choose "Create a passkey", "Add passkey" or similar (some sites offer it during sign-up).</li>
          <li>When the system picker appears, choose <strong>KeyMe Pass</strong> as the storage location.</li>
          <li>Confirm with your <strong>fingerprint, face, or device passcode</strong>.</li>
          <li>The new passkey appears under the <strong>Passkeys</strong> category in KeyMe Pass and syncs to your other devices.</li>
        </ol>
        <figure class="help-figure help-figure-portrait">
          <img src="/screenshoots/help/passkey-create.png" alt="The system credential picker, provided by KeyMe Pass, asking whether to create a passkey for the site" loading="lazy" />
          <figcaption>Step 2: the system asks whether to create the passkey in KeyMe Pass</figcaption>
        </figure>

        <h2>Signing in with a passkey</h2>
        <ol>
          <li>On the sign-in page, choose <strong>"Sign in with a passkey"</strong>, or tap the account field to see suggestions.</li>
          <li>Pick the matching account from the system picker.</li>
          <li>Confirm with your <strong>fingerprint, face, or device passcode</strong> — you are signed in, with no password typed.</li>
        </ol>
        <figure class="help-figure help-figure-portrait">
          <img src="/screenshoots/help/passkey-auth.png" alt="The system sign-in picker listing passkey accounts saved in KeyMe Pass" loading="lazy" />
          <figcaption>Signing in: pick the account, then confirm with biometrics</figcaption>
        </figure>

        <h2>Management and sync</h2>
        <p>Passkeys in KeyMe Pass get the same protection as your passwords and IDs:</p>
        <ul>
          <li><strong>End-to-end encrypted sync</strong>: passkeys are encrypted before syncing to your other devices, so switching phones does not lose them. The server cannot decrypt them.</li>
          <li><strong>Central management</strong>: the "Passkeys" category lists every passkey with its site and account, and lets you delete them.</li>
          <li><strong>Note on deletion</strong>: deleting a passkey in KeyMe Pass <strong>does not remove the record on the website</strong>. To unlink it completely, also remove the passkey in that site's account security settings.</li>
        </ul>
        <figure class="help-figure help-figure-portrait">
          <img src="/screenshoots/help/passkey-list.png" alt="The in-app passkey list; each row shows its site, account and last update, and can be tagged" loading="lazy" />
          <figcaption>The Passkeys category lists every entry and supports tagging</figcaption>
        </figure>

        <h2>FAQ</h2>
        <h3>The site says my passkey is invalid or will not work. What now?</h3>
        <p>Go to that site's account security settings, <strong>delete the existing passkey and create a new one</strong>. We also recommend deleting the stale entry in KeyMe Pass so it no longer clutters the picker.</p>

        <h3>Why doesn't KeyMe Pass appear as an option when signing in?</h3>
        <p>Check the following in order:</p>
        <ul>
          <li>Is KeyMe Pass set as the system <strong>default autofill / passkey service</strong>?</li>
          <li>Does your device meet the <strong>OS version and compatibility requirements</strong> above?</li>
          <li>Does the site or app <strong>actually support</strong> passkeys?</li>
          <li>On macOS, are you using <strong>Safari</strong>? Other browsers do not integrate with the system pipeline.</li>
        </ul>

        <h3>Will passkeys replace my passwords?</h3>
        <p>Not by force. Most sites currently <strong>support both</strong>, so you can keep passwords alongside passkeys and migrate gradually. KeyMe Pass manages and fills both.</p>

        <h3>Can I export my passkeys?</h3>
        <p>For security reasons, passkey private keys are <strong>not included in data export files</strong>. To move to a new device, use <strong>sync</strong> — your passkeys are encrypted and synced to the new device automatically.</p>

        <h2>Known limitations</h2>
        <ul>
          <li>Passkey support is currently in <strong>Beta</strong> and still improving.</li>
          <li><strong>Android</strong>: requires Android 14+ with Credential Manager; unavailable on HMS-only Huawei devices and some China-market ROMs (see above).</li>
          <li><strong>macOS</strong>: available only in Safari and native apps.</li>
          <li><strong>HarmonyOS Next</strong>: passkeys can be viewed and managed, but not used to sign in.</li>
          <li>Site-side passkey support varies; some implementations are still maturing.</li>
        </ul>
      

Passkey Guide


      <h2>Why keep codes here too</h2>
      <p>Many people keep passwords in a password manager and 2FA codes in a separate authenticator, switching between the two at every sign-in. KeyMe Pass can <strong>attach a code to its login entry</strong> so both fill at once.</p>
      <p>Two-factor codes are free and unlimited.</p>

      <h2>Adding a code</h2>
      <p>The "+" button on the vault screen offers two MFA entries:</p>

      <h3>Scan a QR code (easiest)</h3>
      <p>When a site turns on two-factor authentication it shows a QR code. Choose "MFA · Scan" and point the camera at it; every parameter comes across automatically.</p>

      <h3>Add by hand</h3>
      <p>For when there is no QR code, only a string. That field accepts <strong>either an <code>otpauth://</code> link or a Base32 secret</strong> — paste whichever you have.</p>
      <p>Two fields are required: the <strong>account</strong> and the <strong>secret</strong> — neither can be left blank. The account is whichever username or email the code belongs to, which is what tells several accounts at the same service apart.</p>
      <p>"Provider" is optional and just labels who the code belongs to, which helps when you have many.
      <p>Note there is <strong>a single field</strong> — no need to choose "paste a link" versus "type a secret" first; the app works out which you gave it.</p>
      <figure class="help-figure help-figure-portrait">
        <img src="/screenshoots/help/mfa-manual.png" alt="Manual MFA entry screen; the secret field accepts an otpauth link or a Base32 secret" loading="lazy" />
        <figcaption>The secret field takes either an <code>otpauth://</code> link or a Base32 secret</figcaption>
      </figure>
      <p>⚠️ A bare secret always uses the common <strong>6 digits / 30 seconds</strong>. A few services need 8 digits or 60 seconds; for those you must use an <code>otpauth://</code> link or the QR scan, since a typed secret cannot carry those settings.</p>

      <h3>Import from another authenticator</h3>
      <p>Google Authenticator, 2FAS, Aegis, Raivo and lists of <code>otpauth://</code> links (txt) are supported. See the <a href="/help/import">import guide</a>.</p>

      <h2>Linking to a login</h2>
      <p>Open a login entry and scroll to the MFA section. Two buttons:</p>
      <ul>
        <li><strong>Link existing</strong> — attach an MFA entry you already have</li>
        <li><strong>Create and link</strong> — make a new one and attach it</li>
      </ul>
      <p>Once linked, the current code shows on the login entry itself.</p>
      <figure class="help-figure help-figure-portrait">
        <img src="/screenshoots/help/mfa-link.png" alt="The MFA section on a login entry, with Link existing and Create and link buttons" loading="lazy" />
        <figcaption>The MFA section on a login entry (screenshot shows the Chinese interface)</figcaption>
      </figure>

      <h2>When the secret is not standard</h2>
      <p>A standard Base32 secret is <strong>at least 16 characters</strong> after normalization and contains only <code>A-Z</code> and <code>2-7</code>.</p>
      <p>Some services hand out secrets that do not match. <strong>KeyMe Pass does not reject them — it stores them as given</strong>, and tells you how many were like that when importing.</p>
      <p>The reasoning: rejecting them would lock those accounts out, when they work fine in the authenticator you are coming from. If the generated code turns out wrong, go back and check the secret was copied in full.</p>

      <h3>What is not supported</h3>
      <p>Steam tokens and mOTP are <strong>not supported</strong>. They use non-standard algorithms, so a standard calculation produces the wrong code; importing from another authenticator skips those entries and says so.</p>

      <h2>Common questions</h2>
      <h3>The code is always rejected</h3>
      <p>These codes are generated from the clock, so <strong>an inaccurate device time produces wrong codes</strong>. Check that your system time is set to update automatically.</p>

      <h3>Can codes be autofilled?</h3>
      <p>It depends where:</p>
      <ul>
        <li><strong>Browser extension: yes.</strong> It detects the code field and offers one-click filling, with a countdown.</li>
        <li><strong>Mobile apps: copy and paste for now.</strong> System-level code autofill is not wired up yet — usernames and passwords fill automatically, the code field does not.</li>
      </ul>

      <h3>Do MFA entries sync?</h3>
      <p>Yes, through the same encrypted sync as everything else (a membership feature). The browser extension syncs passwords, codes and passkeys.</p>

      <h2>Related</h2>
      <ul>
        <li><a href="/help/autofill">Autofill guide</a></li>
        <li><a href="/help/import">Supported import sources and formats</a></li>
      </ul>
    

Using Two-Factor Codes (MFA)


      <h2>What you can store</h2>
      <p>A vault holds more than website passwords. The "+" button in the bottom right creates any of these:</p>
      <table>
        <thead><tr><th>Type</th><th>For</th></tr></thead>
        <tbody>
          <tr><td><strong>Login</strong></td><td>Credentials for a site or app, with URLs and a linked 2FA code</td></tr>
          <tr><td><strong>MFA</strong></td><td>Two-factor codes, added by QR scan or by hand</td></tr>
          <tr><td><strong>Passkey</strong></td><td>For passwordless sign-in</td></tr>
          <tr><td><strong>SSH key</strong></td><td>Key pairs for server access</td></tr>
          <tr><td><strong>Secure note</strong></td><td>Any text you would rather not keep in plain sight</td></tr>
          <tr><td><strong>Payment card</strong></td><td>Bank and credit cards</td></tr>
          <tr><td><strong>ID document</strong></td><td>Passports, licences and the like, with photos and expiry reminders</td></tr>
        </tbody>
      </table>

      <h2>Folders versus tags</h2>
      <p>These are often treated as the same thing. They are not:</p>
      <table>
        <thead><tr><th></th><th>Folder</th><th>Tags</th></tr></thead>
        <tbody>
          <tr><td>How many per item</td><td><strong>At most one</strong></td><td><strong>Up to five</strong></td></tr>
          <tr><td>Nesting</td><td>No, one level only</td><td>Not applicable</td></tr>
          <tr><td>Good for</td><td>"Where it belongs"</td><td>"What it is like"</td></tr>
        </tbody>
      </table>
      <p>For example: a work email account goes in the <strong>Work folder</strong> and carries the <strong>tags</strong> "frequent" and "important".</p>
      <p>So: <strong>folders for the broad split</strong> (work / personal / finance), <strong>tags for the cross-cutting dimensions</strong>. Anything you want to slice two ways at once is a job for tags.</p>

      <p>Eight built-in tags come with the app: social, finance, shopping, email, games, work, study and developer tools. You can rename and recolour them but <strong>not delete them</strong>; tags you create yourself can be deleted freely.</p>
      <p>Tags come in fifteen preset colours, and KeyMe Pass suggests tags based on an entry's URL and name.</p>

      <h3>Favorites</h3>
      <p>A star on the item, with its <strong>own favorites page</strong> collecting starred entries of every type. Keep it for the handful you reach for daily — the value of that list is that it stays short.</p>

      <h2>Search</h2>
      <p>Once you have a lot of entries, search beats any amount of filing. The box at the top matches names, usernames and similar fields.</p>
      <p>In practice: <strong>favorites for the daily few, search for the rest</strong>. Filing is mostly for your own peace of mind — there is no need to find the perfect folder for every entry.</p>

      <h2>Custom fields and field templates</h2>
      <p>When the built-in fields are not enough, add <strong>custom fields</strong>. If the same set recurs — say every membership card needs "number + expiry + support line" — save it as a <strong>field template</strong> and apply it next time.</p>
      <p>⚠️ A template stores <strong>field names and types only, never the values</strong>. Applying one gives you a set of empty fields to fill in.</p>

      <h2>Attachments</h2>
      <p>Logins, secure notes, ID documents, payment cards, MFA entries and SSH keys can all carry attachments of any file type. Passkeys cannot.</p>
      <p>Attachments use the cloud space that comes with membership.</p>

      <h2>Deleting, and the recycle bin</h2>
      <p>Deleted entries go to the <strong>recycle bin</strong> rather than disappearing, and can be restored at any time.</p>
      <p><strong>The recycle bin has no expiry</strong> and is never emptied automatically. Accidental deletions are therefore recoverable indefinitely — but clearing it out is something you do yourself (it supports deleting everything at once).</p>
      <p>Permanent deletion also removes the entry's local files, such as document photos and attachments. That step cannot be undone.</p>

      <h2>Related</h2>
      <ul>
        <li><a href="/help/mfa">Using two-factor codes (MFA)</a></li>
        <li><a href="/help/import">Supported import sources and formats</a></li>
      </ul>
    