Ext Ops Panel
Open dashboard
Permissions and history

Is Base64Coder: Base64 Decode, Encode & JWT Inspector safe to install?

Base64Coder: Base64 Decode, Encode & JWT Inspector asks for 2 browser permissions and declares no blanket site access. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Base64Coder: Base64 Decode, Encode & JWT Inspector

Chrome extension by Dmitry Rodevich · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 2 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Data collection
Declares it collects none
Audience
291 users · 5.0/5

What data it declares

The developer declares that it does not collect or use your data.

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

No site access is declared in the manifest, so it cannot read the pages you open on its own.

Routine for an extension

Pages it runs its code on

It runs its own code on every page you open: the manifest declares a content script for all sites.

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Runs its code on every site.

The typical extension there declares 3 browser permissions; this one declares 2 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

291 users

Users
+10 since 01.09
278-317 · 33 readings
  1. 2026-09-01281
  2. 2026-09-02285
  3. 2026-09-04291
  4. 2026-09-06293
  5. 2026-09-07291
  6. 2026-09-09292
  7. 2026-09-13289
  8. 2026-09-15295
  9. 2026-09-16284
  10. 2026-09-21286
  11. 2026-09-25307
  12. 2026-09-27317
  13. 2026-09-28316
  14. 2026-10-04302
  15. 2026-10-08290
  16. 2026-10-09291
  17. 2026-10-10293
  18. 2026-10-11288
  19. 2026-10-13289
  20. 2026-10-16298
  21. 2026-10-17291
  22. 2026-10-18292
  23. 2026-10-19293
  24. 2026-10-21292
  25. 2026-10-22291
  26. 2026-10-23288
  27. 2026-10-24283
  28. 2026-10-25278
  29. 2026-10-26282
  30. 2026-10-28291
  31. 2026-10-29294
  32. 2026-10-30296
  33. 2026-11-01291

What the store shows

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

Dmitry Rodevich, who publishes 4 listings we track. This listing has been in the store since 2022-02-16 and was last updated on 2026-09-01.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. Dev Toolkit — by freetoolspot No permissions at all · No permissions declared 4 users
  2. Encode & Decode: Base64, URL, HTML & JWT No site access · 1 permission 5 users
  3. DevTools Decoder No site access · 1 permission 30 users

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Base64Coder: Base64 Decode, Encode & JWT Inspector access?
No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 2 browser permissions.
What data does Base64Coder: Base64 Decode, Encode & JWT Inspector collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Base64Coder: Base64 Decode, Encode & JWT Inspector asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Base64Coder: Base64 Decode, Encode & JWT Inspector publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-11-01.

Back to Base64Coder: Base64 Decode, Encode & JWT Inspector · Alternatives to Base64Coder: Base64 Decode, Encode & JWT Inspector

Where the data comes from: how the catalog is built