
Check the requested ImageKit post-transformation type and its fields before assuming that the uploaded source is defective. ABS streams, thumbnails and ordinary transformations use different documented types. Post-transformations are asynchronous, so an accepted upload is also a separate milestone from each requested output becoming available.
Key Takeaways
- Use abs for streaming and thumbnail for a video still.
- Ordinary video transformations use transformation rather than those special types.
- Track and inspect each requested post-transformation separately.
Read the actual transformation request
Keep the uploaded source identity and inspect the request sent by the implementation. The official pre/post transformation guide defines a post array containing typed transformation objects.
For video, it distinguishes abs, thumbnail and transformation. Its table requires post.type, requires post.protocol for abs, and uses post.value for an ordinary transformation. The listed ABS protocol values are hls and dash.
Do not label an arbitrary crop string as an ABS request and expect the service to infer the intended output. The ABS guide supplies the separate representation contract and its transformation restrictions.
Match each desired file to its type
| Intended output | Documented post type | Separate check |
|---|---|---|
| HLS or DASH stream | abs | Protocol and representation configuration |
| Still video thumbnail | thumbnail | Selected still and actual image |
| Ordinary processed rendition | transformation | Intended transformation value |
The same source lists gif-to-video for GIF image uploads. Do not apply that type to every video input simply because MP4 is the desired result.
Follow the documented serialization for the chosen Upload API or SDK. The guide calls out serialization of post data; adding another JSON string layer without inspecting what the client sends is not a dependable fix.
Track readiness per output
ImageKit says post-transformations are always asynchronous. Its webhook documentation provides success and error events and says each post-transformation has its own notification.
Have the authorized implementation associate those events with the correct source and requested transformation. Record failures as failures rather than repeatedly uploading the same large source because one output is missing.
For a hypothetical campaign, the thumbnail might be available while the stream is still unresolved. Neither state establishes the other. The approved-version guide helps keep processing status distinct from editorial approval.
Inspect the actual deliverables
Retrieve the intended output through the real receiving route. For the thumbnail, inspect content and crop; the poster guide explains its relationship to playback. For ABS, inspect the manifest and representative playback rather than accepting a stored source preview.
Close the approved-file handoff record only when every promised output has its own identity, readiness evidence and review result. This procedure reports no upload, webhook receipt, generation time or stream test.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Why Does a Video Card Show a Black Image Before Playback?
Sources and scope
- ImageKit: Pre and post-upload transformations: Post transformation types include abs, thumbnail, transformation and gif-to-video with type-specific fields. Post transformations are always asynchronous; success/error webhooks are separate per post-transformation.
- 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.