
ImageKit Player has global transformation settings and per-video source settings. The official overview says source-level transformations can override player-level transformations. Two videos inside the same player therefore do not necessarily share the same crop recipe; inspect each source configuration before modifying the media.
Key Takeaways
- Player defaults and source-specific instructions are separate configuration layers.
- A playlist's visual consistency needs explicit source review.
- Correct precedence does not guarantee that one crop suits every film.
Compare the runtime source records
Record the global ImageKit transformation configuration and the source object for each affected video. Use the actual configuration supplied to the player, not only a screenshot of the design or the original source filenames.
The ImageKit Player overview distinguishes global options from source options and says transformations can be added or overridden per video. Its source options are also used for playlist and recommendation items.
A hypothetical studio playlist may contain a landscape interview and a portrait teaser. The shared player can present both while each source carries different processing. That observation would not show that the original film changed on disk.
Resolve the intended default and exceptions
Write the rule before editing: which treatment should be shared, and which videos need their own composition? Compare that rule with the global configuration and each source's transformation field.
Use the installed SDK's documented configuration model to correct an unintended override. The captured overview establishes the global/per-source distinction; it does not justify inventing a universal deep-merge rule for every transformation array. If a combination is unclear, reduce a non-sensitive sample to one known default and one explicit source setting.
The shared-settings allowlist guide supports the editorial decision to keep source-specific framing separate from a common look. Its Lightroom controls are not this player's configuration API.
Keep playback layout separate from processed framing
Read the actual delivered video dimensions and inspect the player's display area. A source transformation and the page's visible layout can affect different parts of the experience.
The aspect-ratio guide helps distinguish an intentional crop, distortion and bars inside the encoded picture. Do not stretch a portrait merely to make two playlist cards look identical.
If ABS is enabled, also respect the documented streaming transformation restrictions. A source-specific setting is not automatically valid simply because the configuration object accepts a field.
Verify the playlist through its real transitions
Play each intended source, move to the next item and inspect the actual crop, face clearance, captions and beginning and ending. Retain the correct source identity so an apparent crop difference is not really another revision.
Keep the approved-version record with the shared default and deliberate exceptions. The SDK is documented as beta, so pin and review the actual version in use. Accept when every source receives its intended treatment and remains visually suitable; this procedure reports no player execution or cross-version behavior test.
Related tasks
- Which Photo Edits Should I Copy to a Whole Set, and Which Should Stay Individual?
- What aspect ratio should I use when uploading an AI film to YouTube?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- ImageKit: Video Player SDK overview: The beta player supports global and per-source transformations, with per-video override. For private/restricted resources, signerFn signs each requested resource through a server-side signing endpoint, including posters, seek thumbnails and subtitles; secrets must not be embedded in the browser.
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.