What's new · Version 1.2.0

PDFs in seven more writing systems.

PageCarry 1.2.0 draws Arabic, Hebrew, Hindi (Devanagari), Thai, Chinese, Japanese and Korean in the PDF. Before this version, a page in one of these languages came out almost blank.

17 November 2026 · Version 1.2.0 is rolling out through the Chrome Web Store. Chrome updates extensions on its own, so you get it without doing anything.

What was wrong before

A PDF can only show a letter if a font inside the file has a shape for it. Until now, PageCarry carried fonts for Latin, Greek and Cyrillic letters only. On a Japanese or Arabic page every letter was left out. What remained was the outline of the page: list numbers, punctuation and the occasional Latin word or number, and on right-to-left lines even those came out reversed (2026 printed as 6202). PageCarry counted the missing characters and said so in its window, but the file itself was not useful.

Left: an Arabic page saved by PageCarry 1.1.0, with only dots, brackets and numbers. Right: the same page saved by 1.2.0, with the Arabic heading, paragraphs and list fully drawn from right to left.
The same Arabic test page from PageCarry's test suite, saved by version 1.1.0 (left) and 1.2.0 (right).
Left: a Japanese page saved by PageCarry 1.1.0 is an empty sheet. Right: the same page saved by 1.2.0 shows the heading and two paragraphs of Japanese text.
A Japanese test page. In 1.1.0 nothing at all was drawn, because the page has no Latin letters.

What 1.2.0 draws

Seven PDF pages saved by PageCarry 1.2.0: Arabic, Hebrew, Hindi, Thai, Chinese, Japanese and Korean, each with a heading, paragraphs and a list.

The text is real text, as in every PageCarry PDF. On our test pages we checked that the words come back correctly when you copy them, in Poppler (pdftotext) and pdf.js (the viewer inside Firefox) for all seven scripts, and in macOS Preview for all but Korean. For Arabic, pdf.js returns the right words but not always in reading order. Copy and search in Chrome's own PDF viewer is still on our manual test list for these scripts.

For Hindi, Thai, Chinese, Japanese and Korean we also compared where lines break with how Chrome breaks the same text. On our test pages they match, except after hyphens in Latin words: Chrome may break a line there, PageCarry does not.

Still local. Nothing extra is downloaded.

The new fonts ship inside the extension. They are open-source Noto Sans fonts (SIL Open Font License): Noto Sans Arabic, Hebrew, Devanagari, Thai, SC (for Chinese and Japanese) and KR (for Korean). When you save a PDF, PageCarry does not download a font and does not send your page to a server. It reads a font from its own files only when the page contains that script, and puts only the characters the page uses into the PDF.

That choice has a cost: the extension is bigger. The Chinese font alone is about 7.8 MB and the Korean font about 2.7 MB, so the installed extension is now a little under 16 MB. We picked this over fetching fonts from the internet, because making a PDF should need no network request except for the page's own images. The privacy policy describes all of it.

What is still missing

We would rather tell you now than have you find out in a saved file.

No native speaker has reviewed these scripts yet. We tested with our own sample pages and compared the output with Chrome and with the shaping engine Chrome uses. If a word looks wrong in your language, please tell us and include the page address if you can share it.

How to try it

  1. Add PageCarry to Chrome, or wait for Chrome to update it to 1.2.0.
  2. Open a page in one of the seven scripts, for example a Wikipedia article in Arabic, Hindi or Japanese.
  3. Click the PageCarry icon and choose Save as PDF.

More: all the ways to save a webpage as PDF in Chrome.

Add PageCarry to Chrome