Support and contact

No. This is a property of the architecture rather than a limitation that can be waived. An uploaded file exists only in server memory for the duration of the conversion and is purged once the result has been delivered to the browser. No copy, cache, backup or log of the file is created at any stage, and no member of staff is able to retrieve it afterwards. Customers should retain their own original until the converted result has been checked.

Three causes account for the majority of failures. The file may exceed the size limit applicable to the plan in use, which is 250 MB on the free tier. The file may not be in the format indicated by its extension, which commonly occurs where a file has been renamed manually. Or the source file may itself be damaged, which can be verified by opening it in the application that produced it. Where none of these apply, please send the details listed above and the fault will be reproduced.

Please provide the tool page used, the exact error message displayed, the source format with an approximate file size, and the browser and operating system. Please do not attach the file itself. The service is designed so that documents are never retained, and transmitting one by email would place it outside that protection. Where a fault can only be reproduced with one specific file, please advise us and a safe alternative will be proposed.

Every upload is validated before processing, and files presenting a genuine risk are refused rather than converted. The usual causes are an archive containing executable files or scripts, a document containing an embedded macro, or a file whose internal structure does not correspond to its extension. In several archive tools risky entries are neutralised rather than the job being refused: the content is preserved but renamed so that it cannot be executed inadvertently, and an accompanying notice sets out what was changed.

The two indicate different conditions and require different handling. A 429 accompanied by rate_limited indicates that the requests-per-minute allowance or the monthly quota has been exceeded. A 429 accompanied by concurrency_limited indicates that too many of the customer’s own jobs are executing simultaneously, and the client should wait for one to complete. A 503 accompanied by server_busy indicates that the service as a whole has reached capacity and is not attributable to the key in use. All three responses include a Retry-After header, which should be honoured rather than the request being retried immediately.

In many cases it can, and reports of this kind are the principal source of improvements to conversion quality. Certain format pairs are inherently lossy: a PDF has no concept of editable paragraphs and a bitmap has no concept of vector paths, so an exact round trip is not always achievable. Please specify the tool used and the precise nature of the defect, such as substituted fonts, displaced layout or omitted pages, and we will confirm whether it is correctable or a constraint of the format itself.

Please write from the address registered to the account and the change will be actioned the same business day. No cancellation fee applies and no retention process is imposed. Cancellation takes effect at the end of the period already paid for, and the API key remains operational until that date. A 14-day money-back guarantee also applies: write within 14 days of a purchase or renewal and the payment is refunded in full. See the Refund Policy for details.

Yes. Please apply through the privacy channel and specify which of the two is required. The security page sets out the in-memory architecture, the sandboxing arrangements and the validation pipeline. The privacy policy states precisely which data is held for paid accounts, namely an email address, a hashed password, plan details and billing records, and confirms that nothing relating to converted files is retained.