Which page-saving extensions actually run on Firefox for Android?

Firefox for Android has supported extensions since 2023, and that is the one thing Chrome for Android still cannot do at all. So the interesting question is not whether extensions run there — it is how many of the ones you would actually reach for do. We checked 248 of them.

Retrieved 2026-08-02 · addons.mozilla.org API v5 · raw data

What was measured

Eight search terms were run against the add-ons search API — full page screenshot, save page as pdf, webpage to pdf, screenshot pdf, capture page, print to pdf, save webpage, page capture — two result pages each, duplicates merged. An extension counts as declaring Android support when the current version lists an android entry in its compatibility data.

Result

Of 248 extensions, 60 declare Android support. Their combined user base is roughly 997,616 daily users, but that number is dominated by a handful of large ones — the median is 221 users.

The fifteen most-used extensions declaring Android support
ExtensionDaily usersRating Min. Android version
Search by Image445,5124.6 (1818)115.0
Read Aloud: A Text to Speech Voice Reader214,5743.8 (1272)113.0
'Improve YouTube!' 🎧 (For YouTube & Video)102,0054.3 (894)120.0
SingleFile85,7244.8 (1029)113.0
Turn Off the Lights for Firefox63,1444.6 (700)120.0
PDF Mage16,5263.3 (315)48.0
Print to PDF13,3283.5 (129)57.0
Save Screenshot10,8024.5 (126)120.0
ChatGPT to PDF9,5484.5 (51)120.0
WebScrapBook6,7924.0 (144)120.0
Save PDF5,5733.3 (115)56.0
Print for Firefox3,8393.8 (22)120.0
PageSaver - Webpage to PDF or Image2,2003.7 (9)120.0
Sprint — YouTube Speed Booster2,1663.9 (30)120.0
Diigo Web Collector - Capture and Annotate1,9153.8 (244)48.0

Declaration is not function

This is the part that matters, and it is why the number above should not be read as a ranking. A manifest entry means the extension may be installed on Firefox for Android. It says nothing about whether the feature works there.

Capture extensions are especially exposed to this. A full-page capture needs to scroll the document, wait for lazy-loaded images, stitch segments and hand the result to a file picker — and every one of those steps behaves differently on Android. The min. Android version column hints at the split: entries at 48 or 57 predate the current extension platform on Android entirely and were carried over, while 113 and above were set after Firefox reopened the platform in 2023.

We did not install or test any of these on a device. Verifying sixty extensions on real hardware is a different piece of work, and until someone does it, nobody — including us — can claim which of them actually deliver a usable file on a phone.

What this means for the claim "one of the few"

It does not hold. 55 of the extensions found here are page-saving or capture tools with Android in their manifest, together around 172,160 daily users. SingleFile alone has 85,724. Our own extension, Full Page PDF Snap, is one entry among them, and its three daily users put it at the very bottom of that list.

We had that claim in our own store listing until this measurement. It is being removed. The accurate statement is narrower and still useful: the extension does run on Firefox for Android, and that puts it in a minority of roughly a quarter of the tools people search for when they want to save a page — not in a category of its own.

Why Chrome does not appear here

Chrome for Android cannot install extensions at all. That is not a gap in this measurement; it is the reason the measurement only covers Firefox. If you want a page saved as a file on a phone, with an extension, Firefox is currently the only mainstream browser where the question even arises.

Questions

Does a higher minimum Android version mean better support?

It means the entry was set recently, nothing more. An extension declaring 113 or 120 was updated after Firefox reopened the Android platform, so its author at least saw the current environment. An entry of 48 was written for a platform that no longer exists in that form.

Which of these actually work?

Unknown, and we will not guess. If you test any of them on a device and want the result published here with your method, the issue tracker is open.