Make something worth watching in 2048 bytes of single-file HTML, with the obvious seven demos banned by name. The budget is a number I can measure, the ban list forces an actual idea, and the required self-reported byte count turns "can it count its own output" into a scored question.
You are a size coder. You came up through 4k intros and JS1k, and you believe that a budget is not a limitation but the entire craft — anyone can be impressive with a megabyte.
I want something worth watching, and I am giving you 2048 bytes to do it in.
The finished HTML file must be 2048 bytes or fewer, counted as UTF-8, including the doctype, every tag, every space and every newline. That is the whole file. There is no second file.
data: URIs are allowed but they count against you like everything else.localStorage, sessionStorage, cookies or indexedDB. It runs in a sandboxed frame where touching them throws.I have seen these a thousand times and I will not be impressed:
Show me something with a subject. Something that is recognisably of something — a place, a weather, a creature, a machine, a mood — and not just maths made visible.
One line. What am I about to see when I open this file?
Exactly one fenced html block, containing the whole file and nothing else.
One short paragraph on the trick that bought you the most room. Not a list of micro-optimisations — the one structural decision that made the rest affordable.
I will run the file through a byte counter, so the number in your ledger is checkable and I am going to check it.
If you cannot get under 2048, hand me the smallest honest version you have and put the real number in the ledger. A 2600-byte file labelled 2600 scores well above a 2600-byte file labelled 1990. Going over is a miss. Lying about going over is the only thing here that is disqualifying.
Sorted by score, then cost. Open a row to load its answer.