Placeholder Images for Automation & API Workflows

Automation workflows need images that can be generated on demand from a simple HTTP request. This preset covers the four most common image slots in automated pipelines: OG images for documentation, wide banners, square avatars, and compact thumbnails.

Size reference

NameDimensionsDescription
og1200x630OG image — 1200×630px, social share preview image for automated documentation
banner1200x400Banner — 1200×400px, wide header banner for emails, READMEs, and landing pages
avatar200x200Avatar — 200×200px, square profile image for database seeds and test fixtures
thumb400x300Thumbnail — 400×300px (4:3), compact thumbnail for content lists and API responses

Why these sizes matter

Manual image downloads break automation workflows. The PlacePack REST API turns every image in this preset into a single GET request — no authentication, no UI, no manual steps. CI pipelines can generate or verify fixture images automatically. Database seed scripts can embed API URLs. Documentation generators can reference placeholder images by URL.

Use cases

Database seeding

Reference PlacePack API URLs in database seed scripts for development and staging. Every environment gets the same deterministic images without managing local files.

README and documentation images

Embed PlacePack API URLs directly in Markdown README files. The API returns stable images with no rate limit concerns for low-traffic documentation pages.

CI fixture generation

Use the POST /api/v1/pack endpoint in a CI step to generate or refresh the fixture set. Compare the downloaded ZIP hash against the committed fixtures to detect drift.

FAQ — Frequently asked questions

How do I generate these images via the API?
Use GET /api/v1/{spec}.{format} for individual images or POST /api/v1/pack with a JSON body containing the size list. No authentication required.
Can I use PlacePack API URLs in database seeds?
Yes. The API returns stable images for any given spec. You can store the URL as the image_url field value or download the image once and store the binary. Both approaches work.
What is the difference between downloading a ZIP and using API URLs?
Downloaded ZIP files are committed to the repository and require no runtime network access — better for CI stability. API URLs work everywhere but introduce a network dependency at runtime.

Ready to generate Automation & API placeholder images?

Open the generator with this preset pre-loaded and download your pack in seconds.