Ext Ops Panel
Open dashboard
Permissions and history

Is Page to Image - Screenshots & PDF safe to install?

Page to Image - Screenshots & PDF asks for 5 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.

Page to Image - Screenshots & PDF

Chrome extension by OpenKirill · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 5 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 specific sites only
Data collection
Declares it collects none
Publisher
No store badges
Audience
133 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

Specific sites only: 1 match pattern.

Worth knowing

Routine for an extension

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 1 site pattern.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Productivity · Tools, 20% of extensions ask for access to every site. This one: Access to specific sites only.

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

133 users

Users
+121 since 31.08
12-133 · 35 readings
2026-09-03: released 0.5.72026-09-15: released 0.7.02026-09-21: released 0.9.14
  1. 2026-08-3112
  2. 2026-09-0213
  3. 2026-09-0414
  4. 2026-09-0716
  5. 2026-09-0818
  6. 2026-09-1021
  7. 2026-09-1328
  8. 2026-09-1530released 0.7.0
  9. 2026-09-1633
  10. 2026-09-2038
  11. 2026-09-2139released 0.9.14
  12. 2026-09-2541
  13. 2026-09-2739
  14. 2026-09-2838
  15. 2026-10-0446
  16. 2026-10-0849
  17. 2026-10-0952
  18. 2026-10-1057
  19. 2026-10-1156
  20. 2026-10-1361
  21. 2026-10-1679
  22. 2026-10-1781
  23. 2026-10-1882
  24. 2026-10-1986
  25. 2026-10-2089
  26. 2026-10-2195
  27. 2026-10-22104
  28. 2026-10-23106
  29. 2026-10-24112
  30. 2026-10-25117
  31. 2026-10-28123
  32. 2026-10-29121
  33. 2026-10-30124
  34. 2026-11-01133
  35. 2026-11-02133

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.

  1. Asked for more permissions (6, was 5)
  2. Asked for more permissions (5, was 4)

Versions we have seen

  1. Version 0.9.14 · Asked for more permissions (6, was 5)
  2. Version 0.7.0 · Asked for more permissions (5, was 4)
  3. Version 0.5.7

Who publishes it

OpenKirill. This listing has been in the store since 2026-08-21 and was last updated on 2026-09-21.

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. GetFullPage — Full Page Screenshot No site access · 4 permissions 484 users ★ 5.0
  2. Scrolling Screenshot & Full Page Capture Tool No site access · 4 permissions 69 users ★ 5.0
  3. Screencrafter - Full Page Screenshot Tool Runs its code on every site · 6 permissions 6 users ★ 5.0

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 Page to Image - Screenshots & PDF access?
Specific sites only: 1 match pattern. It declares 5 browser permissions.
What data does Page to Image - Screenshots & PDF 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 Page to Image - Screenshots & PDF asked for more permissions over time?
Its permissions changed 2 times while we watched, most recently on 2026-09-21.
Does Page to Image - Screenshots & PDF 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-02.

Back to Page to Image - Screenshots & PDF · Alternatives to Page to Image - Screenshots & PDF

Where the data comes from: how the catalog is built