
ImageKit Adaptive Bitrate Streaming does not accept ordinary width, height, aspect-ratio, format, codec or quality transformations in the ABS request. Select its documented sr representations instead. Those representations preserve the source aspect ratio through at_max resizing, so a portrait rendition should not be judged against an assumed landscape rectangle.
Key Takeaways
- ABS representation selection is a different contract from a single fixed-size encode.
- The forbidden parameters are w, h, ar, f, vc, ac and q.
- Check actual rendition geometry and playback, not only a quality label.
Identify whether the address requests a stream or a file
Keep the approved source and record whether the implementation requests a normal video file, an HLS manifest or a DASH manifest. Do not carry every parameter from a working MP4 rendition into an ABS request automatically.
The ImageKit ABS guide describes the sr representation list and explicitly excludes the seven transformation parameters above. It says other transformations remain available, but that is not a guarantee that every arbitrary combination meets a particular account or asset requirement.
For a hypothetical portrait film, a request can contain an otherwise sensible width setting that conflicts with the streaming contract. Re-exporting the source repeatedly would not repair that request.
Select supported representations without forcing the axes
Use the documented sr list for the intended HLS or DASH workflow. Record which representations the player should offer and which original source they belong to.
ImageKit states that ABS representations use at_max and that output matches the original video's aspect ratio. Its table includes familiar landscape resolutions, but those entries should not be treated as a promise that every portrait source becomes exactly 1280 by 720.
The aspect-ratio guide explains why stretching people or baking in bars is an editorial geometry decision. A HandBrake resolution ceiling is another workflow, not an alternative syntax for ImageKit's ABS manifest.
Separate preparation from representation approval
The official guide documents an initial 202 Accepted while variants are prepared and a ready manifest response afterward. That preparation state is distinct from an invalid transformation combination.
Have the implementation owner inspect the actual response and requested manifest. Do not assume a fixed waiting period will correct a forbidden parameter. Likewise, a returned manifest does not prove that every rendition has the expected crop or visual quality.
Inspect representative stream output
Review actual rendition dimensions and picture proportions, then play the film through the intended player. Check faces, captions and movement at the required viewing sizes. Include a real viewer path rather than judging only a stored master thumbnail.
If playback waits for a click, the autoplay guide addresses browser policy at another stage. Accept the ABS configuration when its permitted parameters, selected representations and delivered framing match the brief. No manifest-generation time, buffering improvement or stream test is claimed here.
Related tasks
- How to Set a HandBrake Resolution Limit Without Accidental Upscaling
- What aspect ratio should I use when uploading an AI film to YouTube?
- Why Does My Website Video Play Only After a Click?
Sources and scope
- ImageKit: Adaptive bitrate streaming: ABS uses sr representations with HLS or DASH. The forbidden transformation list is w, h, ar, f, vc, ac and q; representations use at_max and preserve source aspect ratio. Initial manifest preparation returns 202 before a ready 200 response.
Documentation-based guidance from the cited official pages captured on October 25, 2026. Scenarios and acceptance procedures are proposed, not executed tests. No account operation, measured demand, AI-citation frequency, processing benchmark or search-indexing outcome is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.