Always current: automatic updates and the thumbs.store API.
A downloaded thumbnail is a snapshot. The moment a provider restyles a game or ships a new title, that snapshot is out of date — and nobody on the ops team gets a memo. thumbs.store is built the other way round: the art is a live endpoint, not a file you own a stale copy of.
Most lobbies treat thumbnails as assets: you get a folder of images, you upload them, and they sit in your CDN until someone notices they look wrong. The trouble is that casino game art is not static. Providers refresh logos, swap key visuals for anniversaries, and push new titles every week. Every one of those changes quietly turns a tile in your lobby into a snapshot of how the game looked months ago.
Thumbnails as an endpoint, not a download
On thumbs.store a thumbnail has a stable address. You reference it by the game and the size you need, and the service returns the current render. When a provider updates their artwork, the change propagates from one source — you do not re-download anything, and you do not re-cut anything. The tile your players see is always the latest version of that game, in your house style.
That single-source model is also what makes new releases painless. When a provider adds a title, it enters the catalogue and becomes available at its own address automatically. There is no “art backlog” between a game being integrated and a game being displayable, because the art is generated the moment the game’s assets land.
One call, a whole lobby
The API is deliberately boring, which is the point. You ask for a game’s thumbnail at a given size and you get a URL you can drop straight into your grid:
GET /v1/thumb/{game}?size=portrait
→ https://cdn.thumbs.store/…/portrait.webp
Request the same game at landscape, wide or square and
you get the matching layout — same frame logic, different geometry. Pull a provider’s
entire line-up in one listing call and you have a lobby’s worth of art without a single
image passing through a designer’s hands.
Cache it, but never go stale
You can cache or re-host for latency — serving from your own CDN close to your players is fine. The difference is that the canonical thumbnail keeps refreshing, so a cache is a speed optimisation, not a point where your art freezes in time. Set a sensible TTL and your lobby stays fast and current. Provider updates reach your players on your schedule, not whenever someone remembers to redo the folder.
What this removes from your week
- No “the logo changed” tickets — the tile already changed.
- No launch-day art scramble — new games arrive with thumbnails attached.
- No format migrations — a new size is a query parameter, not a re-export.
The result is a lobby that behaves like software instead of like a design deliverable: something that updates itself, scales with the catalogue, and never shows a player a dead tile.