Skip to content

Extension permissions

Why FullPageSS needs browser access.

Chrome permissions can sound broader than they are. Here is every permission FullPageSS requests, in plain English — what it does, when it applies, and what it explicitly does not allow.

activeTab

Read the page you asked to capture

Why it is needed
A screenshot of a page requires reading that page. activeTab is the narrowest permission that allows it.
When it is used
Only at the moment you click the FullPageSS icon, press the keyboard shortcut, or choose a capture from the right-click menu.
What it does not allow
It gives no access to your other tabs, no access before you invoke the extension, and no access afterwards. FullPageSS cannot sit in the background reading pages.
scripting

Run the capture script in that one tab

Why it is needed
The capture routine has to measure the page, scroll it and manage sticky elements from inside the page itself.
When it is used
Injected on demand for a single capture, then removed. There is no content script running on pages you browse normally.
What it does not allow
Nothing is injected into pages you have not asked to capture, and no code is loaded from a remote server.
storage and unlimitedStorage

Save your screenshots and settings on your device

Why it is needed
Screenshots, thumbnails, history and preferences are stored in your browser. A single full-page capture can exceed Chrome’s default 10MB allowance, which is what unlimitedStorage lifts.
When it is used
Whenever you capture a screenshot or change a setting.
What it does not allow
This storage is local to your machine. It is not synced to us and we have no way to read it.
offscreen

Assemble the final image reliably

Why it is needed
Stitching a very large image takes seconds, and Chrome can shut down an extension’s background worker mid-task. An offscreen document is a background page Chrome will not interrupt.
When it is used
Only while a capture is being assembled, copied or downloaded. It is closed immediately afterwards.
What it does not allow
It is never shown to you, never loads a webpage, and cannot see anything except the screenshot being built.
downloads

Save a screenshot to your computer

Why it is needed
Used to write the finished image to your Downloads folder with a readable filename.
When it is used
Only when you click Download, or if you have chosen "download automatically" after capture.
What it does not allow
FullPageSS does not read your existing downloads or your download history.
contextMenus

Add capture options to the right-click menu

Why it is needed
So you can start a capture without opening the popup.
When it is used
The menu entries exist whenever you right-click a page.
What it does not allow
Adding a menu item gives no access to page content on its own.
Access to our licence server

Confirm a Pro subscription

Why it is needed
Pro is unlocked by a licence key, which has to be checked against our licence server.
When it is used
When you activate a key, and at most once a day afterwards to confirm the subscription is still active. Never on the free plan.
What it does not allow
The request contains your licence key, an activation id and an installation label. It never contains a screenshot, a page URL, page content or anything about your browsing.

What FullPageSS deliberately does not request

FullPageSS does not request the tabs permission or access to all websites. That is why Chrome does not warn you that it can “read your browsing history” — it genuinely cannot. The trade-off is that a capture can only start from the toolbar icon, a keyboard shortcut or the right-click menu, which is a limitation we accept in exchange for the narrower permission.

Read the full privacy policy