More about this extension

Note: This is a port of the firefox extension Password Hasher. This extension has the same output as the firefox extension.

Also, the original maker of this extension is located at And in his words, this is what the extension does (Note: This is not an exact clone, and some features are missing. They have of course been removed from the list).

* Automatically generates strong passwords.
* One master key produces different passwords at many sites.
* Upgrade a master key without updating all sites at once.
* Supports different length passwords.
* Supports special requirements, such as digits and punctuation.
* Supports restricting a hash word to not use special characters.
* Extremely simple to use!

Change Log:

- Now allows bumping of sitetags (Easier password changes, go from google to google:1, google:2, ect.).

- Automatically saves settings on a per-site basis
- Some minor bug fixes

Older Versions

  1. Version 0.1
    Compatible With
    Developer Builds
    Developer Builds (Linux)

    Better security without bursting your brain

    Change Log:



  1. Devon says:

    Very nice, but Installation didn’t work because you forgot to add the default_title :-p

    I had to manually edit the manifest.json file and add
    “default_title”: “Blabla”

    Anyway seems to work now.

    Would it cause much trouble if you could use the original layout from

    One more suggestion, please use an extension graphic. (the only that shows up in chrome://extensions 🙂

    Other than that… 5/5 🙂 TY

  2. Me says:

    hm.. seems comments are blocked 🙁

  3. mnuagent says:

    Great I’ve been waiting for this. Getting closer and closer to not needing FF

  4. Kris says:

    Thanks for the input, I will add those to the nextversion. But any reason to use the HTML version, I am trying to model it after the Firefox extension rather than the html page.

  5. Kris says:

    Well, not exactly. SuperChromePass uses different methods of generating the password. I made this extension mainly for people going from firefox to chrome using the password hasher extension in firefox. This extension duplicates that one, except for a few features (Which I am working on)

  6. Marco Buongiorno says:

    Why are comments here blocked for DAYS? 😐

  7. damian says:

    when you’ve typed in the key, and clicked on the field to generate the hash, how do you get that hash into the password field? You can’t copy/paste it, and it doesn’t auto-populate like the firefox one – help?

  8. doeiqts says:

    Don’t make it populate the subdomain. Or at least make it an option to do it rather than the default. So it would grab “google” rather than “”.

    Add a way to import site tags from either firefox or the portable page.

    Add a way to generate a portable page from chrome.

  9. Andy says:

    How do you copy the generated hash into a password field? Te ability to drag & drop it into a field would also be good.

  10. Oren says:

    I’m exactly the target audience – I have been using password-hasher extensively in Firefox and have dozens of sites that use the generated passwords. This has been keeping me from switching to Chrome as I’d have to reset the passwords or go through manual hoops every time I want to log in.

    This extension *almost* solves the problem. The key feature missing is the ability to easily get the generated password from the extension into the password field. Right now, there doesn’t seem to be any way to do it – not even manually, because copy-and-paste doesn’t work and when you click in the password field to fill it, the extension with the generated password disappears from view. The easiest way to fix this would be to have a “copy to clipboard” button on the extension.

    A second and related missing feature is the ability to launch the extension from the context of the password field. The original password-hasher allowed both annotating the field with a button and also just clicking Control-F6 to launch it. This is related to the first point because it allowed the extension to know where the field was in the DOM, so it could automatically copy the generated password into it. This made it very usable – Ctrl-F6, type in the master password, enter, enter, done.

    Currently the extension lives “globally” in the top bar so it can’t tell which password field it should auto-populate. Someone suggested the ability to drag the password from the extension and drop it into the password field, which IMO wouldn’t be as nice as the original password-hasher approach, but may be an adequate solution to the problem.

    Either way, as of version 0.2 this is a nice proof of concept but isn’t actually usable. Still great work though. I eagerly await a future usable version that would allow me to switch to Chrome. Thanks Kris for doing this for us!

Write a Review