## TL;DR

For ImageKit signed URLs, encode the URL first and then sign it, per the docs, not the other way round. And if a transformation does not exist in your SDK, build the URL string by hand from the documented transformation codes, the SDK may simply not expose it.

## Steps

1. For ImageKit signed URLs, encode the URL first and then sign it, per the docs, not the other way round.

2. And if a transformation does not exist in your SDK, build the URL string by hand from the documented transformation codes, the SDK may simply not expose it.

## When to use

You are seeing this: For ImageKit signed URLs, encode the URL first and then sign it, per the docs, not the other way round. Use this skill when you run into "ImageKit signed URLs: encode before signing".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.