How long are my files stored?

The file storage duration is totally under your control. This article describes what are the file storage options and discuss the most popular use cases for that.

Convert without storing the file

When you use the StoreFile=false setting (which is the default), the conversion occurs entirely in memory, and no file is written to disk or stored on our servers. The converted file is streamed directly back to you in the API response as raw bytes, so no persistent storage occurs. In this mode, there’s zero data retention.

For additional security, we restart all Kubernetes instances every two hours to purge memory.

Store file for 3 hours

When source files must be converted multiple times, conversion performance can be improved by uploading files once and converting them multiple times without re-uploading them (see workflows). Another benefit of the uploaded file is that conversion requests can be formed just by the URL query (no need for the multipart formatter).

When you set StoreFile=true, the converted file is stored securely on our servers for up to 3 hours. After that, it is automatically deleted. You can also delete it manually whenever you choose.

Our servers are secured with encryption at rest and in transit. All data is processed in a secure, isolated environment, and access is controlled via a private URL with a UUID appended.

Only authorized users with the private URL can access and download the file. The URL is private and should not be shared publicly.

The file is stored for a maximum period of 3 hours after conversion. You can delete the file manually as soon as you have downloaded it.

Store the file and delete it immediately after the conversion

If you choose to store a file on our server, you can delete it immediately once you are done converting. Otherwise, it will be automatically deleted after 3 hours.

Updated on: 10/02/2026