What the extension does
The popup is a small Base64 workbench:
- Encode and Decode switch the direction. Encoding takes any Unicode text as UTF-8.
- URL-safe, No padding and data: URI shape the encoded output for URLs, JWTs or HTML.
- Selection pulls the text you selected on the current page into the input.
- Copy puts the result on the clipboard, and the character counts show the size of input and output.
Decoding accepts the standard and the URL-safe alphabet, with or without padding, and ignores line breaks. When the input is not valid, the popup says which character is wrong and where. When the decoded bytes are not UTF-8 text, it shows them as hex instead of garbled characters.
Right-click to encode or decode
Select text on any page and right-click. The menu has Encode with base64hub and Decode with base64hub; either one opens the popup with your selection loaded and the result ready to copy. This is the quickest way to read a Base64 value in a log viewer, an API response or a config file without copying it into another tab.
Permissions and privacy
| Permission | Why it is needed |
|---|---|
contextMenus | adds the two right-click menu items |
activeTab, scripting | read the selected text on the tab where you clicked, only at that moment |
storage | remember your options and cache the footer slide |
There are no host permissions, so the extension cannot read pages in the background. It has no analytics and loads no remote code: everything it runs ships inside the package Chrome reviews.
The one network request is for the footer slide: the popup fetches a short list of items from https://base64hub.com/data/ext/v1/<language>/items.json and caches it for 24 hours. The request carries nothing you typed, and the items are shown as plain text.
Extension vs btoa in the DevTools console
The classic shortcut is btoa() and atob() in the console. They handle Latin-1 text and the standard alphabet, and fail on everything else:
btoa("Привет") // InvalidCharacterError: btoa accepts Latin-1 only
atob("-_-_") // InvalidCharacterError: no URL-safe alphabet
The extension encodes text as UTF-8, reads both alphabets, and does not need DevTools open. For images and files, which a popup is too small for, use Image to Base64 or File to Base64 on this site; they also run entirely in your browser.
The extension docs cover every option.
FAQ
How do I decode Base64 in Chrome without opening a website?
With the extension installed, select the Base64 on the page, right-click and choose Decode with base64hub. The popup opens with the selection already decoded.
What permissions does the base64hub extension need?
storage, contextMenus, activeTab and scripting, and no host permissions. It can read a page only when you invoke it there, and only to fetch the text you selected.
Does the extension work in Firefox or Edge?
It is made for Chrome 127 and later and distributed through the Chrome Web Store only. In other browsers use the Base64 encoder on this site, which needs no installation.
Why does the extension show an ad?
The popup has one small slide at the bottom, marked Ad, that keeps the extension free. It is a plain-text link with no scripts or tracking, and it never sees what you encode.