Paperly
Upload PDF

Service status

Last updated: August 2026

Because Paperly processes files in your browser, nearly every tool works without any server dependency. This page runs a live availability check of the site and explains what that does — and does not — tell you.

Current status

Operational

Checked at 05:00:00 AM (your local time).

  • Website and static assets
  • Status endpoint

PDF tools run entirely in your browser, so tool processing does not depend on this endpoint.

The check above is performed by your browser against this live deployment when you open the page — it confirms the site is reachable right now. It is not a 24/7 incident dashboard with a history. The automated health check that runs on a schedule alerts the maintainers when something fails, and this page will always say so honestly if the endpoint cannot be reached.

What depends on a server

Only loading the website itself needs the network. Once a tool page is loaded, processing happens locally — so a tool can keep working even if our servers experience issues, as long as the page is already open.

How to check a tool yourself

  1. Open the tool page directly instead of through a search result — the URL ends with the tool name.
  2. If the page loads but a tool errors, it is almost always the file, not the site: try a different file.
  3. If the page itself does not load, check your network connection and try a private window.
  4. Still broken? Report it with the tool name, browser and error message.

Status definitions

StatusMeaning
OperationalThe component is working as expected in the current release
DegradedAvailable but slower or with reduced capability
MaintenanceTemporarily unavailable while we make changes

Because every component is served by the same deployment, the check reports “Operational” when the site is reachable. Individual PDF tools are not separately monitored — they run locally in your browser.

FAQ

This page runs a live availability check when you open it. It is not a monitored dashboard with an incident history — the automated health check (scripts/healthcheck.mjs) runs on a schedule and alerts the maintainers directly when it fails.