Skip to content
CoverKit CoverKit v0.1.13

Clearing cache

Use these actions when a template design or use case mapping changed but previews or the front end still show old artwork.

After a successful clear, CoverKit shows an admin notice that images will be regenerated on the next view.

From the template edit screen

Section titled “From the template edit screen”
  1. Open Media → CoverKit and edit the template.
  2. Find the Cache Management meta box (usually in the sidebar).
  3. Click Clear Cache.

CoverKit removes cached images for that template so the next preview or front-end request builds new files.

This clears the template preview folder (coverkit/{template-id}.* under the CoverKit cache) and any post-bound outputs that reference that template ID in the filename.

From the template list

Section titled “From the template list”
  1. Go to Media → CoverKit.
  2. Select one or more templates (checkboxes).
  3. Choose Clear Cache from the bulk actions dropdown.
  4. Click Apply.

Use this when you updated several templates and want to refresh all of them at once.

List table preview vs. full clear

Section titled “List table preview vs. full clear”

The template list may offer a preview action that reloads a thumbnail without clearing every cached variant. If the preview still looks wrong after a design change, use Clear Cache (single template or bulk) for a full refresh.

When to clear

Section titled “When to clear”
SituationAction
Changed layers, colors, or canvas sizeClear cache on that template
Changed use case mappings or settingsClear cache on that template
Open Graph URL still shows old art on your siteClear cache, then reload the image URL
Social network still shows old thumbnailCoverKit cache is already fresh; wait or use the platform’s share debugger

Automatic invalidation

Section titled “Automatic invalidation”

Saving or deleting a template, or updating dimension presets under Settings → CoverKit, clears related cache entries automatically. You only need manual clearing when something still looks stale.

Saving or deleting a post clears only that post’s cached images (post/{post-id}/ under the CoverKit cache), not every post on the site.

Where files are stored

Section titled “Where files are stored”

All generated files live under wp-content/cache/coverkit-{id}/ on your server, where {id} is a fixed six-character code unique to your site (derived from the WordPress AUTH_KEY in wp-config.php). The folder name is not meant to be secret, but it is harder to guess than a single shared coverkit directory if wp-content/cache is reachable over HTTP.

KindExample path (under cache/coverkit-{id}/)When it is used
Post use-case outputpost/4861/5748-opengraph.jpgFront-end or REST image for a specific post and use case
Template preview (editor)coverkit/5748.pngTemplate editor or list preview when no post is bound (post_id = 0)
Composition (internal)_cache/generator/ and _cache/generator/elements/Layer and canvas reuse between renders; cleared on a full cache clear

Post outputs include the template ID in the filename so clearing one template does not remove another template’s images for the same post.

Images are still served through CoverKit REST URLs, not as direct links to these cache paths.

After upgrading CoverKit

Section titled “After upgrading CoverKit”

When you update to a version that uses the site-specific cache folder, CoverKit starts writing to cache/coverkit-{id}/ immediately. Files left under the older wp-content/cache/coverkit/ folder are not moved or deleted by the plugin.

  1. Use Clear Cache in the template editor or bulk actions (or rely on automatic invalidation when you save templates) so previews and front-end images regenerate in the new location.
  2. Optionally delete the legacy wp-content/cache/coverkit/ folder on the server to free disk space once you have confirmed everything looks correct.
Section titled “Related”