PxKV.com reads the way developers already write: px for pixels, the unit every stylesheet uses, and KV for key-value store. Pixels in a key-value store. That’s what the product behind the name does.
It’s one binary that stores original images by content hash and serves resized versions on request, in modern formats like WebP and AVIF. Upload a photo once. Ask for it 400 pixels wide in AVIF, and the server makes that version and caches it. Upload the same image twice and it’s stored once, because its hash doesn’t change.
Why every site wants one
Images are usually the heaviest thing on a web page, and the largest one often decides how fast the page feels. Search engines measure that. Serving a right-sized AVIF in place of a full-size JPEG cuts the bytes dramatically and makes a site visibly quicker on a phone. Plenty of sites still skip it, because the tooling is fiddly.
Hosted image CDNs built big businesses on this exact problem, and their prices climb with traffic. A self-hosted image server under a short, technical name gives developers a way to own that layer. Content addressing keeps storage tidy, and immutable URLs let any CDN cache the results forever.
It also makes a site easier to move. Images stored by hash don’t depend on any one site’s folder structure, so a rebuild or a platform switch leaves them intact, and one archive can feed several sites at once.
The name suits an open-source project with a hosted tier, an image CDN startup, a hosting company adding media handling or a developer-tools brand. It’s four letters on a .com, and a developer decodes it at a glance.
Every page has pictures. Few of them are the right size.