Set up a reusable ImageKit named transformation and reference it in delivery URLs instead of repeating transformation strings
domain: imagekit.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In the ImageKit dashboard, go to Image Settings > Named Transforms and define a name for a transformation string (e.g. width/height/blur parameters)
Reference the named transform in delivery URLs using the `tr:n-<name>` path segment in place of the raw comma-separated transformation string
Combine named transforms with additional ad hoc parameters in the same URL where supported, keeping frequently reused presets centralized while allowing per-request overrides
For video assets, confirm the named transform applies since named transformations work across both image and video delivery
If stricter governance is required, enable the account setting that restricts delivery to only named transformations, blocking arbitrary unnamed transformation strings in URLs
Known gotchas
Changing a named transformation's underlying definition changes the output for every URL referencing that name retroactively — there's no per-URL version pinning
Restricting an account to named-transformations-only will break any existing URLs built with raw/unnamed transformation strings, so audit existing usage before enabling that restriction
Named transforms are account-wide, so naming collisions across teams sharing one ImageKit account can unexpectedly change delivery behavior for unrelated assets
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?