
Unpublishing one current ImageKit file is not the same selection as unpublishing all its versions. Review the Include file versions option and any separate public review links when withdrawing a client asset. Confirm the actual access outcome after the asynchronous operation instead of treating a library status change as complete withdrawal evidence.
Key Takeaways
- File publication state and version-selection scope are separate.
- Publish/unpublish operations are asynchronous.
- Public review links need their own access review.
Inventory the representations being withdrawn
Official ImageKit Draft Assets documentation describes files and versions that can be published or unpublished. The publish/unpublish dialog has an Include file versions option when the state change should cover all versions.
The page says a file version's URL changes when it transitions between draft and published states because its ik-obj-version query parameter changes. Keep a record of the actual referenced versions rather than assuming one remembered URL covers the entire history.
Make an access-scope checklist
- Identify the current asset and earlier versions that must be withdrawn.
- List ordinary delivery URLs and known public review links separately.
- Confirm that the account offers the relevant draft/publication controls.
- Have the authorized owner select the intended files and version scope.
- Observe completion of the asynchronous publish/unpublish operation.
- Check the resulting state in the asset details.
- Verify the intended recipient access through each relevant route.
The documentation limits a publish/unpublish action to at most 100 files. Do not infer that selecting a larger project necessarily changed every item.
Do not confuse cache scope with access proof
The provider documents a purge request on unpublishing, including cache handling for other versions. It also distinguishes path-parameter transformations, whose caches persist, from query-parameter transformations, which are purged.
That cache statement alone does not establish the response an unauthorized request receives. Record the actual route and result rather than promising that every old rendition has vanished.
A hypothetical portrait withdrawal
A client withdraws a portrait from public use while the studio retains it for private project records. The proposed audit checks the current image, any earlier public version and a previously created review link.
Official ImageKit public-link documentation says a single-file public link can expose its file regardless of publication status. A draft state is therefore not evidence that a deliberately shared review surface was closed.
Acceptance and remaining copies
The review-link closure guide explains that access closure does not recall ordinary downloaded files. This procedure adds version-aware publication state and the provider's separate review surface.
Accept only the withdrawal scope supported by observed access checks. If an old route remains usable, keep it unresolved and use the provider's supported controls or support process. No account state, link or publication setting was changed or tested for this article.
Related tasks
- Does Revoking a Review Link Remove the Images Someone Already Downloaded?
- How to Make a Public Wedding Teaser From a Private AI Film
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- ImageKit: Draft assets: Draft/publication states apply to files and versions; Include file versions scope, asynchronous operation, batch limit, version-URL changes and path/query cache behavior.
- ImageKit: Public links: View-only external review links allow downloads, omit library classifications/comments, show current versions only, and have documented password/time/draft-exposure controls and single-file publication-state exception.
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.