ConvertAll is built around a simple public workflow: choose the route, upload one file, wait for the processing step to finish, review the output, and download the result before the retention window expires.
The most important decision happens before the file is uploaded. The route page defines what the system expects as input and what kind of output tradeoffs are likely on the other side. This is why ConvertAll uses explicit pair pages instead of a single undifferentiated converter form.
After a valid file is selected, the system stores it temporarily and creates a short-lived task record. The public page then shows queue and processing states so users can see whether the job is waiting, actively converting, or ready for download.
A completed result still needs verification. Depending on the route, conversion can change layout, transparency, compression, fonts, metadata, timing, or embedded assets. The file may be technically valid while still being the wrong output for the real publishing or delivery context.