Effective immediately, Cloudflare Images can ingest TIFF files, expanding the set of source formats that the service can store and transform. For teams that already use TIFF as a master asset for photography, scanning, or archival, the change removes the need for a separate conversion step before uploading to the platform.
Supported workflow changes
Once a TIFF is stored, Images can dynamically generate compressed variants in the most efficient format for each client request, such as WebP or AVIF. The service also supports on‑the‑fly resizing without altering the original file, preserving the high‑resolution source for future use.
Operational considerations
Adopting TIFF as an input format influences several operational aspects:
- CI/CD pipelines can skip pre‑conversion of master assets, reducing build time and storage overhead.
- Only the first page of a multi‑page TIFF is processed; any additional pages are ignored, so workflows that rely on multi‑page content must extract needed pages beforehand.
- Existing limits and supported output formats still apply; teams should review the current limits documentation to ensure their use cases remain within bounds.
Security and compliance notes
Introducing a new file type expands the surface for content‑type handling. While the source does not call out specific security changes, practitioners should verify that any scanning or validation tools in their pipeline are updated to recognize and safely process TIFF files, guarding against malformed payloads that could affect downstream services.
Related CloudNinjas coverage: hands-on guides.
What This Means For Practitioners
Evaluate your asset ingestion pipeline to see if the TIFF‑to‑WebP/AVIF path can replace existing conversion steps. Update CI scripts to upload raw TIFFs directly to Images, and confirm that your monitoring captures any failures when only the first page is rendered. Finally, ensure your security tooling is aware of TIFF handling to maintain a consistent defense posture.
