AI Summary
Status
The status page is the place to check whether a failure is platform wide or specific to your file, account, or browser. It should help users understand the difference between an incident and a local problem, not just show a generic green badge.
What this page covers
Status pages are only useful when they answer a basic question: is the platform failing for everyone, or is this problem just happening to me? This page explains how to think about that split and what to do next.
Support channels
Support ticket system
Open a support ticketBest for tool failures, account issues, billing questions, and anything that needs screenshots or follow up.
Support email
unifypdfsupport@gmail.comUse email when you need to share context, file names, or reproduction steps outside the app.
Useful for quick questions and status checks. For anything sensitive, use the ticket system or email instead.
What the status page is for
Use the status page to check for known incidents involving core uploads, worker based conversion routes, account systems, or support infrastructure. If there is a live incident, the goal is to say so clearly instead of making every user rediscover the same issue in isolation.
If the status page looks normal but your file still fails, the issue is more likely to be input specific, browser specific, or tied to an external provider used by that workflow.
What normal service does and does not mean
A normal status badge does not guarantee every input file will succeed. PDF conversion, uploads, media downloads, and scans can still fail because of file structure, restrictions, provider limits, or unsupported formats.
What normal service does mean is that there is no known broad outage affecting the majority of users at that moment.
When to open a ticket anyway
Open a ticket when the same issue repeats, when output quality is clearly wrong, or when a business critical workflow is blocked. That is true even if the public status page shows everything as operational.
A ticket is also the right move when a problem involves billing, account access, or a file that needs private discussion rather than public status messaging.
Related pages
Closing note
A good status page sets expectations, but it should never replace direct support when a real workflow is still blocked.