№ 10//Field note/2 min read

a model small enough for a browser tab

Image models kept failing at 16×16 sprites, and scaling up language models failed too. So we built something much smaller: 440,000 weights, no server, about $80 of GPU time.

The pxl site: rows of 16×16 pixel-art sprites (a crown, a mushroom, an owl, a knight) around the headline "A small model. For 16 × 16 sprites." and a prompt box reading "knight".
pxl.brigada.dev, drawing in your browser.

Can a model small enough to run in a browser tab do something useful? We spent a week finding out.

Edion Limani on our team wanted to build a game, and image models kept failing him: a different palette every time, no real grid underneath. So we built pxl, a small model that draws 16×16 sprites in your browser. No server, no API bill.

The obvious route failed. We fine-tuned language models at 600M, 1.7B and 4B parameters. They drew clean pixel art that was never what we asked for: 0 recognisable out of 88 prompts.

A language model writes one piece at a time, but a sprite is a square. So we stopped scaling up and built something much smaller.

The result is 440,000 weights in a 5.5 MB download. One sprite in four comes back clearly recognisable. Claude, the model that taught it, manages about half from a data centre. The whole experiment cost about $80 of GPU time.

That's how we build for clients too. Start with the data you already have, train a model you own, and run it on your own private servers. Your data never leaves and there's no per-request bill. A pilot takes weeks, not quarters.

Try it: pxl.brigada.dev.

Brigada.dev
Prishtinë, Kosovo
← Back to home
More from the journal
№ 14we're one seat shortHiring№ 13in a client's wordsField note№ 12from architect's files to a live 3d siteField note