Image caching
CoverKit generates images once and reuses them so pages and previews load faster. Generated files are stored on your WordPress server (not on an external image SaaS).
What is cached
Section titled “What is cached”When a template or use case produces an image URL, CoverKit can save the rendered file and serve that copy on later requests until the cache is cleared or invalidated.
Cached images include outputs tied to templates and contexts CoverKit renders (for example Open Graph images and canvas embeds on the front end).
When images refresh automatically
Section titled “When images refresh automatically”You usually do not need to clear cache manually when:
- You save or delete a CoverKit template
- You change dimension presets in Settings → CoverKit
Those actions invalidate stored images so the next view regenerates them.
When to clear cache manually
Section titled “When to clear cache manually”Clear cache when:
- You changed the design or field mappings but still see an old preview or front-end image
- You are debugging and want to force a fresh render
See Clearing cache for step-by-step actions in wp-admin.
CoverKit cache vs. social platform cache
Section titled “CoverKit cache vs. social platform cache”Clearing CoverKit’s cache only affects files on your site.
Facebook, LinkedIn, Slack, and other networks cache link previews on their own servers. After you fix an Open Graph image, a platform may still show the previous thumbnail until its cache expires or you use that platform’s debugging/refresh tool.