Less account hunting.
More testing.

Your test accounts. One place. Ready when you are.
Import a CSV, choose a persona, and fill your approved login page.

Synthetic accounts only · Stored locally

You choose the account. You press Sign in.

See Login Pal in action.

Login PalInteractive demo
Choose an account

Who are you testing as?

Search or filter the sample accounts. Pick one to try a fill.

Staging · sample group3 accounts
qa.example.com

Fictional accounts. This demo never touches a real login.

Sample data only. No installation needed.

Every persona.
One familiar place.

A CSV in one folder. An account in a chat. A role you can’t remember. Bring the accounts you test with into a searchable, local catalog.

Keep each environment together.

Import your CSV into named groups. Keep environments, roles, and account metadata together—and search them in seconds.

Choose accountApproved siteFill fields

A deliberate fill. Every time.

Authorize a domain, choose an account, and fill on your command. You always press the site’s Login button yourself.

Your first login,
step by step.

After installation, import your accounts and authorize a login page. Then choose the account you need.

Installation guide ↗
01 → 02 → 03Import. Configure. Choose.
  1. 01

    Import your CSV.

    Bring your test accounts into a named group. Keep each environment together.

    Setup details

    Open Settings, name a CSV group, and choose your file. Include account_id, username, and password; extra columns become searchable metadata. Set the authorized domain, verify the file, then confirm the import.

    Start with “Download sample CSV (3 rows)” in Settings.
  2. 02

    Configure and authorize your site.

    Choose your login page and match its username and password fields.

    Setup details

    Configure the group’s login profile: your authorized login domain, username and password matching rules, and optional successful-login tracking. Choose a success URL or visible element if you want tracking, then save and approve the site permission.

    Importing accounts alone doesn’t authorize autofill.
  3. 03

    Choose an account and fill.

    Find the persona you need. Fill on your command, then press Sign in yourself.

    Setup details

    Visit the authorized login page and open the extension. Choose a group, search by ID, username, or metadata, and select an account. Review it, choose Autofill, then submit the website’s form yourself.

    “Recent” means filled. “Last successful” means verified.

Your catalog works offline.

Once installed, the extension runs locally. Import a CSV, find an account, organize groups, review history, or export your data—even without an internet connection.

Understand local storage ↗

What works without a connection

  • Import, search, edit groups, and export locally
  • Packaged fonts and scripts—no runtime CDN
  • No cloud account, sync, or telemetry

The website is a separate connection. Detection and autofill need an accessible login page and approved access. A local site can work without the internet; signing into a remote service still depends on that service and your connection.

Privacy & data protection

For synthetic data and testing purposes only. All imported accounts, credentials, and metadata must be created for testing. Do not use real personal data or production credentials. Your catalog stays in your browser; its encryption key is stored in the same browser profile. You control website access, filling, exports, and deletion.

You approve
where it can fill.

Chrome asks before the extension can work on your configured sites. Here’s what that access enables, and what stays in your control.

You choose the sites.

How site access works

Website access is requested when you use Save & authorize website or Detect fields from the login page. Detection can request access to all domains configured for the selected group, including newly added ones.

For missing detection permissions, the extension first names the sites and explains the request. Select Continue to open Chrome’s permission prompt. Importing a CSV alone does not grant site access.

See accepted domains ↗

Read field names. Fill on request.

How the permission is used

Chrome may describe site access as permission to read and change data. The extension uses it to list matching open tabs, inspect login-field attributes, fill your selected account, and observe a success condition if you enable tracking.

Field detection reports labels and identifying attributes, not the values entered into inputs. Autofill delivers only the chosen account to the approved page after your explicit action. It never submits the form.

You can decline or revoke access. Denying the request leaves local account management available, but blocks the site action that needs it. Manage access in Chrome → Extensions → Login Pal → Details → Site access. After revoking access, authorize the site again before detection or autofill.

What about the other extension permissions?
Local storage
Keeps groups, settings, accounts, and history on this computer.
Page scripting
Runs the field-detection and autofill helpers on approved pages; it does not independently grant access to every website.
Active tab
Provides temporary access to the current tab when you invoke the extension, supporting actions tied to that tab. The configured-domain checks still apply.
Clipboard writing
Supports explicit copy actions for account details, including a chosen synthetic password. The extension does not request clipboard-read permission.

Chrome’s host permission is broader than the extension’s rules: it is not limited to your configured path or port. The extension separately checks the exact scheme, hostname, and port. Requested HTTP/HTTPS support does not mean automatic access to all sites.

Chrome permissions ↗

Questions before
your first login?

Will it work with every login page?+

It supports top-level, visible, writable username and password inputs. Embedded frames, closed shadow roots, SSO handoffs, and multi-step logins are outside this version’s scope. Configure and test your own site’s field matching and success signal before relying on it.

Can I use it on localhost?+

Yes. HTTP and HTTPS are supported on local and regular hosts. Authorization matches the exact scheme, hostname, and port. Subdomains need separate authorization; a path does not narrow autofill access. See accepted domains for examples.

What’s the difference between Merge and Replace?+

Merge & Update adds or updates accounts by ID and keeps omitted accounts in the selected group. Wipe & Replace replaces that group’s entire dataset. Invalid rows are excluded, so review the verification results carefully before confirming Replace. Other groups are unaffected.

How do recent and successful logins work?+

Recent records a successful field fill. Last successful changes only when the configured success condition is observed within two minutes. A failed login leaves the previous successful account unchanged. Editing filled values cancels attribution.

What should I know about CSV files?+

Imports support UTF-8 CSV files up to 2 MiB, 10,000 rows, and 100 columns. Account IDs must be unique within a group. Export CSV downloads the entire selected group, including synthetic passwords. Original and exported CSV files remain on your disk; the extension does not encrypt or delete them.

Install Login Pal
in Chrome.

Install the unpacked extension in Chrome 121 or newer. No account to create. No service to connect.

Local installation · not on the Chrome Web Store

Your installation checklist.

Tick each step as you go. Progress stays on this page.

  1. 1
  2. 2
  3. 3
  4. 4
Set up a group ↑

Your next test starts
with the right account.

Install Login Pal ↗

Start with a CSV. Keep the rest close at hand.