MyPwdTool
MyPwdTool can fill your passwords into web pages (and, on iOS and Android, native apps) in several different ways, depending on the platform and the browser. They’re genuinely different mechanisms under the hood, not the same thing rebranded — worth understanding which one you’re actually setting up.
AutoFill Credential Provider (iOS & macOS) — not a browser extension
This is not a browser extension at all — it’s a system-level integration that iOS and macOS themselves support for any password manager. Instead of running inside a specific browser, it plugs directly into the operating system’s own AutoFill mechanism, which means it works everywhere the system offers to fill a password — Safari, Chrome, any other browser, and even inside native apps that have a login screen, not just web pages.
Setup (iOS): Settings app → General → AutoFill & Passwords → set From to MyPwdTool (alongside or instead of iCloud Keychain). Once enabled, tapping a username/password field anywhere on the system offers MyPwdTool’s suggestions directly from the keyboard.
Setup (macOS): System Settings → Passwords → Password Options → enable MyPwdTool as an AutoFill provider. Once enabled, it appears as a suggestion whenever you click into a login field, the same way iCloud Keychain’s suggestions do.
Because this runs as its own separate process from the main app, it unlocks independently — using either your master password or Face ID/Touch ID, per its own copy of your vault, kept in sync with the main app automatically.
AutoFill Service (Android) — not a browser extension either
Same idea as iOS/macOS above: Android’s own system-level Autofill Service framework, not a Chrome extension. Once set as your device’s autofill service, it can offer to fill logins in any app or browser that supports Android Autofill, not just Chrome.
Setup:
- In MyPwdTool, open Settings and tap Enable Autofill. This opens Android’s own system dialog for choosing an autofill service.
- Choose MyPwdTool from that dialog.
Optional, if Chrome doesn’t pick it up automatically: Chrome → ⋮ menu → Settings → Passwords and Autofill section → Autofill Services → Autofill using another service. Chrome restarts itself to apply the change.
Safari Extension (macOS & iOS)
The Safari extension ships bundled inside the app itself — there’s nothing separate to download or install.
Setup: Safari → Settings → Extensions → enable MyPwdTool. On iOS: Settings app → Safari → Extensions → enable MyPwdTool. The first time you use it on a given site, Safari may ask you to grant it permission for that website (or “Always Allow on Every Website”) — this is normal Safari behavior for any extension, not specific to MyPwdTool.
Once enabled, click the extension’s icon in Safari’s toolbar to see matching entries for the current site, or to unlock your vault directly from the popup if it’s locked.
“Couldn’t find a login form on this page,” even though there clearly is one? Some sign-in pages — Apple’s own App Store Connect and developer.apple.com among them — don’t render their login form directly; they load it from a separate, cross-origin domain (an embedded frame). Safari’s per-website permission model doesn’t automatically extend to that embedded domain, so if you only granted MyPwdTool permission for the page you’re on, it silently can’t see the form. Fix: Safari → Settings → Extensions → MyPwdTool → set website access to “Allow on Every Website” instead of granting it site by site. Chrome doesn’t have this limitation, since its permission model applies uniformly once granted.
Chrome, Edge & Firefox Extensions (Windows & macOS)
Add MyPwdTool to Chrome — Chrome Web Store.
Add MyPwdTool to Edge — Edge Add-ons store.
Add MyPwdTool to Firefox — Firefox Add-ons store.
Setup:
- Install the extension from the link above.
- In MyPwdTool, open Settings → Chrome, Edge & Firefox Extensions and click Register for your browser. The app registers itself as that browser’s native-messaging host automatically, using the extension’s published ID.
- If needed, fully quit and relaunch the browser (not just close the window) so it picks up the new host registration.
The first time the extension actually talks to the app, MyPwdTool shows a one-time approval dialog (“Allow extension to connect?”) — accept it only if you just set this up yourself.
On Windows, a locked vault currently needs to be unlocked from the main MyPwdTool window first — unlike Safari, the Chrome, Edge & Firefox extensions can’t yet prompt for your master password directly in their own popup. See Windows App for the rest of the Windows-specific scope.
Testing an unpacked (Developer Mode) build instead of the Store version? Chrome & Edge assign unpacked builds a different extension ID. Use Settings’ “Advanced: use a different extension ID” option to paste that ID instead of relying on the default. Firefox’s ID is fixed regardless of how it’s loaded, so this doesn’t apply there.