PageCarry's Chrome Extension Rebuilds a Signed-In Page as a Real PDF, With Searchable Text and Heading Bookmarks, and Says Nothing Leaves Your Machine but Image Requests

A screenshot of a wiki page is a photograph of text. You cannot search it, copy from it or click anything in it, and a PDF made by capturing pixels has the same problem. PageCarry’s pitch is that screenshots “freeze pixels,” while the extension “rebuilds the page as a document.”

The page labels this “TRUE TEXT,” with the line “Select, search and copy.” Links get their own label, “Keep useful hyperlinks,” and they “stay clickable” in the output. Headings “become PDF bookmarks when the source provides them,” which means the sidebar of the PDF viewer gets a table of contents, but only if the original page had headings to build one from.

There are three modes. The extension can capture “the readable article, the full page, or a selection.” Before saving, a person can pick A4, Letter or one continuous page, a sans-serif or serif typeface, and adjust what it calls “image behavior.” The site does not explain what that setting does.

The signed-in part is the point. PageCarry calls itself “a Chrome extension that turns the page you have open into a PDF,” and because “everything is converted on your device,” it works on pages behind a login and on localhost. An internal wiki, a staging site on your own machine or a customer dashboard can become a file without the page being sent to an online converter. The site says “No page text or browsing history is uploaded,” along with “No accounts and no ads.” A banner reading “LAUNCH” sits beside “Unlimited free clipping,” and no paid plan is listed. A launch label next to the word “free” is a tidy way of saying the price may change.

The privacy page is where the claims get specific. “Content extraction, layout and PDF rendering never send page content anywhere,” it says. The one content-related request it names is for images: “PageCarry fetches the page’s own images to place them in your PDF.” That is a network call all the same, and the policy ties it to the image-embedding setting being on.

There is a second request, and it is optional. Calibration reporting is off by default. “If you opt in, the extension sends one aggregate usage range per month,” to an address on Cloudflare Workers, with no credentials or referrers, no page content and no URLs. The policy also says the extension “does not load remote code, Google Fonts, CDN scripts, or converter software,” so everything it runs is bundled.

Two smaller facts sit in the same policy. Settings, clip counts and a bounded diagnostic log stay in browser storage, and selected settings may sync through Chrome profile sync to other signed-in computers. The site itself “uses no analytics, advertising, accounts or cookies.” The extension’s permissions are not spelled out in the policy, and the site names no maker beyond “© 2026 PageCarry.”

So the privacy claim reads as unusually plain for a browser extension, and it is still the maker’s statement. A reader would have to watch the network traffic to confirm it, and nothing on either page says anyone has.

An extension that touches private pages has to earn trust before it asks for money, and an unlimited launch period is one way to do it. The likely test comes when the “LAUNCH” label comes down: whether the local conversion and the plain privacy page survive the first paid plan.

Screenshot of a wiki page: retired.