Understand service availability, browser requirements, local-processing limits, and the fastest troubleshooting steps.
What the live board checks
The board above calls the public health endpoint from your browser. A successful response confirms the website can reach the application and read its core catalog data. It does not test every possible file, codec, browser API, or device limitation.
Service components
Public pages, the tool catalog, API routes, accounts, blog, administration, and browser processing can fail independently. A site-wide problem usually affects multiple pages. A single-tool problem is more often caused by format details, memory pressure, an unsupported codec, or a browser restriction.
Supported environment
Use a current Chrome, Edge, Firefox, or Safari with JavaScript enabled. Aggressive blockers, old embedded browsers, private-mode storage limits, low-memory devices, and disabled workers can affect downloads or local processing even when the service is online.
Troubleshooting
Refresh once, check the tool’s input and size guidance, preserve the original, and try a small non-sensitive sample. Close unnecessary tabs, keep the device awake, and test another current browser. Never repeatedly retry a huge file if the device is already low on memory.
Report a persistent incident
Send the affected URL, tool, browser and operating-system versions, approximate file size, time of the issue, and exact error. Do not attach confidential files. These details help distinguish a service incident from a format or device limitation.