Convert SVG to TIFF

Pick the largest size you will ever display it at, because this is the step where the file stops being resolution-independent. An SVG is stored as mathematical paths and renders sharp at any size; the TIFF is a fixed pixel grid, and enlarging it afterwards can only interpolate. Export at twice the intended display size if it is headed for a high-DPI screen. SVG renders perfectly at any size, stays editable, is searchable and diffable as plain text, and is usually a fraction of the size of an equivalent PNG. TIFF is the Tagged Image File Format from 1986, and it is the format scanning, publishing and archiving industries standardised on.

In an SVG, text is real text — selectable, searchable and re-styleable, and it needs the font to be available or embedded to render as intended. Converting away from SVG turns that text into pixels or into document text depending on the target; converting towards SVG only produces real text if the source had a text layer to begin with.

No pixel data, no. Both formats store the image without lossy compression, so the picture that comes out is identical to the one that went in and the conversion can be repeated indefinitely. What changes is file size, and which features travel — colour depth, embedded profiles, layers and animation are all supported unevenly between lossless formats.

Transparency survives when TIFF is PNG, WebP, TIFF, GIF, or SVG. Converting to JPG flattens the alpha channel against a white background. If you need transparency in the result, target a transparency-aware TIFF instead of TIFF=JPG.

Embedded ICC color profiles are read from SVG and re-attached to the TIFF output where the format supports it (JPG, PNG, TIFF, WebP). Formats without profile support fall back to sRGB, which keeps colors consistent across most modern displays.

Camera EXIF (ISO, shutter, lens, GPS coords) is preserved by default during SVG → TIFF when both formats support metadata. Use the privacy option to strip metadata before download if you need to share images without geolocation.

Yes — drag multiple SVG files into the upload zone and we queue them in parallel. Free users get 100 MB per file; Premium has no per-file cap and runs more parallel workers, so a 200-image batch typically finishes in under two minutes.

For straight format conversion we run the same libpng / libjpeg-turbo / libwebp / ImageMagick pipelines a desktop editor uses, with the same output quality. The difference is parallel batch handling — desktop apps open one file at a time; we accept a batch.

Default is 1:1 — your TIFF keeps the pixel dimensions of the source SVG. If you need to resize as part of the conversion, use /resize-image/ after conversion, or chain it with the /image-resize/ utility.

For JPG / WebP, quality 75-85 typically gets the TIFF 60-80% smaller than SVG with no visible difference at normal viewing distance. For lossless TIFF (PNG, TIFF), expect smaller savings — usually 5-30% via better deflate / LZW compression. TIFF handles CMYK, 16-bit depth, embedded ICC profiles and multi-page documents, which is exactly what print and archival workflows require.

Yes — uploaded SVG files are processed in isolated workers and deleted within minutes. We never read, store long-term, or share the pixel data. The full retention window is documented at /privacy/.