Ext Ops Panel
Open dashboard
Permissions and history

Is PDF Reader Aloud — Read PDF Out Loud, Text to Speech safe to install?

PDF Reader Aloud — Read PDF Out Loud, Text to Speech asks for 6 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.

PDF Reader Aloud — Read PDF Out Loud, Text to Speech

Chrome extension by Korvel Labs. · Make Chrome Yours · Accessibility

Open in the Chrome Web Store
What the developer says, and 3 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.

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

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

Reaches your browsing data or every site

Routine for an extension

How usual this is for its category

In Make Chrome Yours · Accessibility, 23% of extensions ask for access to every site. This one: Access to every site.

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

880 users

Users
+780 since 01.09
100-880 · 44 readings
2026-10-01: released 1.0.5
  1. 2026-09-01100
  2. 2026-09-02123
  3. 2026-09-04160
  4. 2026-09-05181
  5. 2026-09-07200
  6. 2026-09-08273
  7. 2026-09-10286
  8. 2026-09-13305
  9. 2026-09-15311
  10. 2026-09-16335
  11. 2026-09-21377
  12. 2026-09-25397
  13. 2026-09-26417
  14. 2026-09-28428
  15. 2026-10-04506
  16. 2026-10-08545
  17. 2026-10-09541
  18. 2026-10-10556
  19. 2026-10-11562
  20. 2026-10-13565
  21. 2026-10-16588
  22. 2026-10-17591
  23. 2026-10-18597
  24. 2026-10-19589
  25. 2026-10-20607
  26. 2026-10-21634
  27. 2026-10-22651
  28. 2026-10-23670
  29. 2026-10-24678
  30. 2026-10-25680
  31. 2026-10-26696
  32. 2026-10-28709
  33. 2026-10-29730
  34. 2026-10-30736
  35. 2026-11-01759
  36. 2026-11-02767
  37. 2026-11-04794
  38. 2026-11-06806
  39. 2026-11-07814
  40. 2026-11-08821
  41. 2026-11-09832
  42. 2026-11-10835
  43. 2026-11-11852
  44. 2026-11-14880

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.

Versions we have seen

  1. Version 1.0.5

Who publishes it

Korvel Labs., who publishes 2 listings we track. This listing has been in the store since 2026-08-12 and was last updated on 2026-10-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. Read PDF Aloud: PDF Text to Speech & Voice Reader No site access · 1 permission 476 users ★ 5.0
  2. Text to Speech – Read Aloud Access to specific sites only · 7 permissions, 3 site patterns 7 users
  3. Voice Out: Read Aloud Text to Speech Reader Access to specific sites only · 8 permissions, 5 site patterns 50k users ★ 4.1

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 PDF Reader Aloud — Read PDF Out Loud, Text to Speech access?
Every site you visit. This extension can read and change the content of any page you open. It declares 6 browser permissions.
What data does PDF Reader Aloud — Read PDF Out Loud, Text to Speech 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 PDF Reader Aloud — Read PDF Out Loud, Text to Speech asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does PDF Reader Aloud — Read PDF Out Loud, Text to Speech 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-14.

Back to PDF Reader Aloud — Read PDF Out Loud, Text to Speech · Alternatives to PDF Reader Aloud — Read PDF Out Loud, Text to Speech

Where the data comes from: how the catalog is built