This reference explains what file type Templified produces when a render finishes, where those files live, and what you receive when you download one.
Render output by template type
| Template type | Output format | File extension |
|---|---|---|
| Single-page template | JPEG image | .jpg |
| Two-page template | PDF containing both pages (pages stored as high-quality JPEG inside the PDF) | .pdf |
There is no setting to change the output format — the format is determined entirely by whether the template has one page or two. Single-page templates always produce a JPEG; two-page templates always produce a PDF.
JPEG output (single-page)
The render is a full-resolution JPEG at the pixel dimensions you set when you created the template. Output quality is set at a high level — not maximum (which would produce unnecessarily large files), but high enough that photographic detail is fully preserved for both screen delivery and print production.
The file you download or send is the same file the renderer produced. There is no additional compression or resizing on download.
PDF output (two-page)
Two-page templates render both pages and combine them into a single PDF. Each page inside the PDF is stored as a JPEG rather than lossless pixel data, which keeps photographic PDFs at a practical file size — typically 5–15 times smaller than an equivalent lossless PDF — while preserving print-quality detail.
The PDF contains exactly two pages in the order they appear in the template: page 1 first, page 2 second. No additional metadata, color profiles, or print marks are added.
Where renders are hosted
Every finished render is stored and served from cdn.templified.io, Templified's content delivery network. URLs on this domain are the canonical location of each output file.
When you download a render in Studio, the browser fetches it from cdn.templified.io and saves it to your Downloads folder. When you use the API, the output_url field in the response points to the same domain. When you send a render to Dropbox or a webhook, the file is pulled from this CDN and forwarded to the destination.
Render URLs are permanent — a completed render's URL does not change or expire. You can copy a URL from the History page and use it later. Re-rendering a design (by downloading again or re-sending) produces a new URL for the updated output, but the old URL continues to work.
Download behavior and file names
When you click Download in the template editor or in Studio, Templified:
- Saves any unsaved changes to the design.
- Triggers a render if no up-to-date render is cached, or returns the cached output immediately if one exists.
- Initiates a browser download. A new render takes roughly 15–20 seconds; a cache hit downloads immediately.
The saved file is named after your design — special characters that are not valid in filenames are replaced with underscores. The file extension matches the output type: .jpg for single-page renders and .pdf for two-page renders.
From the History page you can open any completed render in a new browser tab by clicking View next to the job. The URL in that tab is the permanent CDN link you can bookmark or share.
API: the output_url field
API and Zapier render responses include an output_url field when a job is complete. This is a direct link to the finished file on cdn.templified.io. The URL's extension matches the output type — .jpg for single-page, .pdf for two-page — so downstream systems can branch on it without inspecting the file.
For asynchronous renders you poll the job until status is complete, then read output_url. See Polling for async renders for the full polling pattern.
Comments
0 comments
Article is closed for comments.