Ext Ops Panel
Open dashboard
Permissions and history

Is Web Source Extractor safe to install?

Web Source Extractor asks for no browser permissions and 1 site pattern. 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.

Web Source Extractor

Chrome extension by mdmahfujarrahman · Productivity · Developer

Open in the Chrome Web Store
What the developer says, and 1 screenshot

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.

Site access
Access to every site
Data collection
Declares it collects none
Publisher
No store badges
Audience
748 users · 3.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

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

We have not read this listing's manifest since we started keeping permission names. The counts on the card come from the last time we did.

How usual this is for its category

In Productivity · Developer, 30% of extensions ask for access to every site. This one: Access to every site.

The typical extension there declares 3 browser permissions; this one declares no 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

748 users

Users
+204 since 31.08
544-1k · 28 readings
  1. 2026-08-31544
  2. 2026-09-02552
  3. 2026-09-04558
  4. 2026-09-05557
  5. 2026-09-06554
  6. 2026-09-07557
  7. 2026-09-08563
  8. 2026-09-09568
  9. 2026-09-13569
  10. 2026-09-15584
  11. 2026-09-16587
  12. 2026-09-20602
  13. 2026-09-21605
  14. 2026-09-25622
  15. 2026-09-26620
  16. 2026-09-28626
  17. 2026-10-04660
  18. 2026-10-08661
  19. 2026-10-09659
  20. 2026-10-10671
  21. 2026-10-13672
  22. 2026-10-16679
  23. 2026-10-19766
  24. 2026-10-20958
  25. 2026-10-211k
  26. 2026-10-29917
  27. 2026-10-30748
  28. 2026-10-31748

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

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

mdmahfujarrahman, who publishes 2 listings we track. This listing has been in the store since 2025-07-10 and was last updated on 2025-07-10.

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. DevTools - Sources downloader No permissions at all · No permissions declared 4k users ★ 3.7
  2. SiteExtract by Elevven11 No site access · 2 permissions 13 users
  3. Real Page Source No site access · 4 permissions 105 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 Web Source Extractor access?
Every site you visit. This extension can read and change the content of any page you open. It declares no browser permissions.
What data does Web Source Extractor 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 Web Source Extractor asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Web Source Extractor 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-10-31.

Back to Web Source Extractor · Alternatives to Web Source Extractor

Where the data comes from: how the catalog is built