While most file types can be served through imgix, not all of them support imgix parameters.
For example, it's not possible to apply a
w=300 parameter on a
Supported file types
File types can interact with imgix either as input formats or output formats.
An input format is a file that will be accepted by imgix's parameters. You can transform images that are accepted with an input format by using imgix's API (
w=600, for example).
An output format is a file type that imgix can transform any input format into. For example, you can transform a
jpg into a
Any non supported input format will be served without any transformations.
|Filetype||Supported as input format||Supported as output format using
Serving other types of assets with imgix
However, we do not guarantee the behavior of such assets—rendering parameters (especially default parameters) can affect the output and may accidentally output a rendering error.
When serving unsupported file types, it's important to not apply any parameters on the URL. While there's usually no issue with using parameters on unsupported input types, there are some rare instances where a parameter can cause unexpected behavior on certain file types.
If you have a Source configured with default parameter(s) that's causing issues with unsupported input assets, you can work around this issue by either:
- Serving those assets without using imgix or
- Use a separate Source in order to serve those assets
File specific notes
Only supported as a pass through, not as an input type.
HEIC will only work if the original image was created from an iOS device
SVG's can be enabled as an input parameter by contacting email@example.com. If they are not yet enabled for your account, we can pass them through as long as they have a correct XML declaration at the top of the file.
Animated WebP is not yet supported as an input format.
Transparency can be loss when converting a GIF into a WEBM. As an alternative, you can convert the GIF into an APNG to support transparency.