Files and how long we keep them
Each render gives a file URL on files.mintrender.com. We keep the file for 30 days on the Free plan and 365 days on paid plans, then delete it.
File URLs
https://files.mintrender.com/r/{workspace}/{input hash}.{png|jpg|webp|svg|pdf}- The input hash is a SHA-256 of everything that makes the file: the template version, the data, the format, the size, scale, quality and the bytes of every image and font. Nobody can guess the URL.
- Anyone who has the URL can open the file, with no key. Send the URL only to people who may see the file.
- The same input gives the same URL. A file never changes after it is made, so it is sent with
Cache-Control: public, max-age=31536000, immutable. - To get the bytes in your code, download the URL, or render with
?inline=1. - To show the file under your own address, copy it to your own storage.
How long we keep files
| Plan | Files kept |
|---|---|
| Free | 30 days |
| Starter | 365 days |
| Pro | 365 days |
| Business | 365 days |
- The time starts when the file is first made. A later render that reuses the file (
cached: true) does not make the time longer. - An hourly job deletes files whose time has ended. After that, the URL answers 404, and the same request makes the file again and costs a credit.
- The plan when the file is made sets its time. Changing the plan later does not change it.
Other files
| File | Who can open it | Kept |
|---|---|---|
| Uploaded images and CSV files (assets) | Only your workspace, with a key: GET /v1/assets/{id}/file | Until you delete them |
| Images we fetch from URLs in data or a template | Nobody. The render reads them by their hash. | A private copy, reused while it is kept |
| Batch ZIPs | Your workspace, with a key: GET /v1/batch/{id}/zip | Until the batch's last file ends; then zip_url is null |
| Previews (POST /v1/preview) | Only the caller, in the answer | Never stored |
| Signed link answers | Anyone with the link | In Cloudflare's edge cache for 1 hour, and as a normal file |
All files are stored in Cloudflare R2.
Deleting
- Deleting a template stops its renders and signed links at once (404). Files already made stay until their time ends.
- Deleting an asset removes its file. It is refused (409
in_use) while a version of a template that is not deleted uses it. - Deleting your account (Account, Delete my account) removes you from every workspace. Each workspace where you are the only member is frozen at once: its keys are revoked, its queued work is canceled and its subscription ends. An hourly job then removes its files and records, after running renders end.
- If you are the only owner of a workspace that has other members, the delete stops (409
last_owner). Make another member an owner first, or remove the other members.
Seen MintRender used for content that breaks our terms? Report it. Questions about the API: support@mintrender.com, with the request id.