Use cases
A use case defines how a template is used to produce an image—not a separate design on its own.
Content (post, page, site data) → Template (layout) → Use case (output)You always start with a template design, then assign one or more use cases to that template in the CoverKit sidebar. There is no global “handlers” screen: open the template, enable the outputs you need, map fields to layers, and save.
CoverKit is designed to grow into more output types (social sizes, email headers, watermarks, and similar). Today’s built-in use cases are:
| Use case | What it does |
|---|---|
| Featured image | Replaces front-end post thumbnails with a generated image; editor preview in Summary |
| Open Graph image | og:image (and related tags) on eligible front-end views when this template is chosen |
| Sandbox | Editor testing and live preview; every built-in setting control; no public front-end output |
One template, multiple outputs
Section titled “One template, multiple outputs”The same template layout can power several outputs at once—for example a social share preview, a featured image, and a Sandbox assignment for editor testing. Each use case has its own:
- On/off state for this template
- Settings (post types, alt text, dimensions hints, and so on)
- Field-to-layer mappings
Mappings are stored with the template assignment, not as free-floating site options.
Where to configure
Section titled “Where to configure”- Edit a CoverKit template (Media → CoverKit).
- Open the CoverKit sidebar → Use cases.
- Enable a use case, adjust settings, and map Required / Recommended fields to layers.
Step-by-step: How to configure use cases.
Custom and third-party use cases
Section titled “Custom and third-party use cases”Developers can register new use cases in PHP. See Custom use cases and the codebase reference.
Related
Section titled “Related”- Templates
- Template editor
- Caching — when generated images refresh