Secure PDF Viewer Downloads & RevenueSecure PDF Viewer · Google Play
Not in a tracked Google Play top chart right now.
Updated 3 Nov 2026 · rankings refresh through the day
DeveloperGrapheneOS
CategoryProductivity
PriceFree
Released
Installs100k+
Rating★ 4.4 (931)
Updated
Content ratingEveryone
Full timeline · 3 events
- 🆕Secure PDF Viewer first spotted by AppInsiderUnited States (found via search)
- 📦Secure PDF Viewer version 33See https://github.com/GrapheneOS/PdfViewer/releases/tag/33 for the full release notes.
- 🆕Secure PDF Viewer released on Google Play
Collected from the stores by AppInsider since we first spotted the app. Dates are when we saw each change.
Rating
4.4 ★
931 ratings
Measured
Secure PDF Viewer on Google Play
App details
App ID
app.grapheneos.pdfviewer.play
Publisher
GrapheneOS Foundation
Publisher country
Canada
Content rating
Everyone
Secure PDF Viewer downloads
Worldwide, per day, and installs to date. The band is open; the exact number is free with an account.
How this is calculated
Google Play shows an exact lifetime install count; downloads per day are its daily change (measured). When Play hasn't refreshed the count, they come from new ratings and Top Free chart positions. Confidence is the chance the real number is within half to double ours.
Active users
All platforms, worldwide. Free with an account.
Stickiness (DAU / MAU)
how many monthly users open it on a given day
How this is calculated
Monthly users come from lifetime installs across every store, fitted on monthly active user figures companies publish; daily users = monthly × the typical daily/monthly ratio for the category. Confidence is the chance the real number is within half to double ours.
Where it ranks on Google Play
Every top 200 chart it appears in across 23 countries.
| Country | Charts | Rank |
|---|---|---|
| Not in a Google Play top chart right now. | ||
Ratings
Google Play, worldwide.
Rating
4.4 ★
931 ratings
Measured
Ratings
931
Measured
Written reviews
57
Measured
About Secure PDF Viewer
Simple Android PDF viewer based on pdf.js and content providers. The app doesn't require any permissions. The PDF stream is fed into the sandboxed WebView without giving it access to the network, files, content providers or any other data.
Content-Security-Policy is used to enforce that the JavaScript and styling properties within the WebView are entirely static content from the APK assets along with blocking custom fonts since pdf.js handles rendering those itself.
It reuses the hardened Chromium rendering stack while only exposing a tiny subset of the attack surface compared to actual web content. The PDF rendering code itself is memory safe with dynamic code evaluation disabled, and even if an attacker did gain code execution by exploiting the underlying web rendering engine, they're within the Chromium renderer sandbox with less access than it would have within the browser.
Content-Security-Policy is used to enforce that the JavaScript and styling properties within the WebView are entirely static content from the APK assets along with blocking custom fonts since pdf.js handles rendering those itself.
It reuses the hardened Chromium rendering stack while only exposing a tiny subset of the attack surface compared to actual web content. The PDF rendering code itself is memory safe with dynamic code evaluation disabled, and even if an attacker did gain code execution by exploiting the underlying web rendering engine, they're within the Chromium renderer sandbox with less access than it would have within the browser.
What's new in 33
See https://github.com/GrapheneOS/PdfViewer/releases/tag/33 for the full release notes.