
Copying an ImageKit asset does not include its earlier versions by default. The documented copy workflow has an explicit option to copy all file versions; moving includes all source versions. Decide whether the handoff is a current-file copy or a history-preserving transfer before treating the destination as a complete archive.
Key Takeaways
- A correct current picture does not prove its earlier revisions were copied.
- Copy and move have different version-history scope.
- A same-name destination can combine version histories.
Define what the recipient needs
Official ImageKit asset-versioning documentation says the copy operation's all-versions option is unchecked by default, so only the current version is copied. A move includes all source versions.
The page also says that when a copied or moved file encounters a destination asset with the same name, source versions are appended to the destination's history. Do not treat a familiar filename as proof that this is a clean independent archive.
Plan a version-aware handoff
- Identify the source asset and its intended current revision.
- Record whether earlier approved or rejected states are part of the agreement.
- Inspect the proposed destination for an existing same-name asset.
- For a copy that needs history, review the all-versions option in the folder selection drawer.
- Use a disposable sample to establish the intended operation.
- Inspect the destination's version list, not just its current thumbnail.
- Confirm that the correct current image and required earlier versions are present.
Keep unrelated client histories separate. A name collision should trigger an identity review before the operator accepts merged history.
A hypothetical campaign archive
A studio copies a portrait asset into a long-term project area. The current image appears, so the team assumes that its earlier approved crop and correction sequence are also present.
The proposed acceptance check opens the destination's asset details and inspects the version dropdown. It then compares required revision identities against the source record. No version count or successful transfer is claimed in this example.
ImageKit notes that non-current versions do not appear in the library by default. Use the documented version search or asset detail view rather than concluding that a hidden version was deleted.
Separate history inspection from restoration
The versioning page limits several library operations on non-current versions. It separately documents access and transformation through each version's unique URL. Do not restore a version to current merely because a familiar download menu is absent.
The approved-version handoff guide supplies the editorial identity record. This task adds the storage operation's explicit history scope.
Acceptance and limits
Accept when the destination contains exactly the intended asset history and the agreed current rendition. Record unresolved collisions or unavailable versions before calling the archive complete.
The documentation says current and previous versions count toward storage and an asset has a version limit. Review those constraints with the owner before a large transfer. No copy, move, restoration or storage change is reported here.
Related tasks
- Should I Use Canva Version History or Trash to Recover My Work?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Does a Lightroom Classic Catalog Backup Include My Original Photos?
Sources and scope
- ImageKit: Asset versioning: Copy defaults to current version unless all-versions option is selected; move includes source versions; same-name destinations append histories; hidden versions, restricted operations, unique version URLs and storage scope.
Documentation-based editorial synthesis with AI-assisted research and drafting. Scenarios, ledgers and acceptance checks are hypothetical or proposed. No hands-on test, account change, measured demand, AI-citation rate, benchmark or client acceptance is claimed. Availability and plan limits remain within each cited source's scope.
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.