Limits & Known Issues
Limits
| Limit | Value |
|---|---|
| Max upload size | 10 MB per file |
| Allowed formats | PNG, JPEG, GIF, WebP, AVIF; SVG is explicitly blocked (can embed scripts; blocked to prevent XSS) |
| Max output dimension | 5000px per axis |
| Metadata value length | 2000 bytes per field |
| Media library page size | Server caps at 500/request; UI reveals in batches of 60 |
| Upload URL lifetime | Presigned URL valid 5 minutes |
| Auth scope | Bearer token checked for view access only; no fine-grained write/edit permission yet |
Deletion is soft-delete only. Removing an asset hides it from library listings, but previously-issued URLs for that asset keep serving from cache; there is no hard-delete/purge path yet. Don’t rely on deletion for takedown of sensitive content; treat it as “unlisted,” not “removed.” Worth knowing before promising a client that removing an image from the library actually removes it everywhere.
Known issue: large animated GIFs/WebPs
An animated image with a very large total pixel area across all its frames (roughly: a 1200×1200 GIF becomes an issue somewhere past ~70 frames) fails during the transform step with a generic, unhelpful 500 error rather than a clear message. Workarounds: keep animated sources short/low-resolution, or request with no transform parameters at all: the original bytes are always served untouched when no transform is requested, which sidesteps the failure (at the cost of not being able to resize/reformat it).
Not yet available
- No rate limiting on the image delivery endpoint (open by design, for now)
- No org-level or cross-site asset sharing: assets are scoped to a single site, which matters for a multi-brand rollout: a logo or shared asset can’t currently live in one place and be referenced across brand sites’ media libraries
- No “find everywhere this image is used” / bulk-replace tooling
- No customer-definable metadata fields beyond the four fixed names
This guide reflects the plugin as documented; treat the editorial-interface constraints and multi-site limits above as active areas of development, not permanent; worth checking with Pantheon before ruling something out for a multi-brand build specifically because of a limit listed here.