plahold.com: size the layout before the images arrive
Suppose a card grid is ready before its images are. The layout is agreed, the components exist, and every image slot is waiting on a photographer, a CMS import or a designer’s final export. Something has to fill the slot in the meantime. If that something is a folder of temporary JPEGs, the repository carries binary files that were never meant to stay, and someone has to remember to take them out again.
A URL in place of a file
plahold.com fills the slot with an image URL instead. Put a size in the address and the service returns a placeholder at that size, as SVG by default. Add colours, a label and a font when a prototype should look closer to the eventual page, or request PNG, JPG, static GIF, WebP or AVIF when a platform will not accept SVG. The URL builder assembles the address and the inline docs describe the format and its limits. plahold.com is owned by VMCSoft Digital and published and operated by ViWeb Technology.
The property that matters is that the request is deterministic: the same size, colours and label produce the same output. That is what lets a placeholder sit in a component story, a template demo or a README without a binary asset committed beside it. The use-cases page documents six patterns it is built for: responsive grids, template and prototype fills, Open Graph canvases, responsive source sets, CSS backgrounds and documentation or test fixtures.
What a placeholder can and cannot tell you
A placeholder with explicit dimensions lets a team exercise the layout it has chosen at the right shape. The aspect ratio is the one you asked for, and a responsive source set can be tested with candidates whose logical size is written on the image itself. Whether the grid actually holds when the image loads still depends on how the consuming code reserves space; the placeholder gives you a correctly sized candidate to test that with, not a guarantee on its own.
It does not answer content questions. A grey rectangle labelled 800x450 says nothing about whether the final photograph crops well at that ratio or carries the right subject. That review needs the real asset. Generated placeholders are free to use in personal and commercial work, but they are not stock images and they are not finished brand imagery. Treat them as scaffolding and plan the day it comes down.
One further boundary: text in the URL is public, because the URL is public. A label should be a size or a slot name rather than anything you would not print on the page.
Replace before the content review
A placeholder is a convenience for work in progress, so keep track of where each one lives. Name the slot in the label and the replacement list writes itself. Before the final content review, search the codebase for the domain, swap each hit for the real image and confirm the layout still holds with actual files. That leaves production free of live dependencies on temporary assets, and free of anything shaped like a placeholder.
The next time a layout is ready before its images, give each slot a URL at the right size and keep the repository free of files that were never meant to stay.