Why async matters

Image conversion can be CPU-heavy and bursty. Async jobs keep the web request short, move heavy processing to the worker layer and make retries explicit.

What the client should do

The client sends a file and target format, receives a job id, then tracks the result. That is usually simpler and safer than trying to keep a long synchronous upload-processing-download cycle inside a single request.

When it is worth paying for API access

The API becomes valuable when conversions are part of your product, internal ops or recurring customer delivery. At that point the cost of repeated manual work is usually higher than the plan itself.