Main Page

From SizeCoding
Jump to: navigation, search

Welcome to SizeCoding.org!

SizeCoding.org is a wiki dedicated to teaching programmers the various techniques used to create tiny demoscene intros. While these techniques can be used for other applications (boot sectors, ROM, BIOS and firmware code, etc.), the information presented here is firmly oriented towards the demoscene. Practicality and common sense are sometimes thrown out the window just to shave a single byte.

For those unfamiliar with the demoscene or demoscene effects, here is:

Now with that said, here is the list of active platforms available on this wiki:

Oldschool 8-bit / 16-bit platforms:


As well as modern platforms like:

  • Fantasy consoles - TIC-80, PICO-8, MicroW8
  • Windows - Sizecoding for Windows: 1K and 4K intros.
  • DOS - Sizecoding for X86 / DOS.
  • Javascript - Sizecoding for Browsers / JavaScript
  • Processing - Sizecoding using Processing
  • Linux - Sizecoding for Linux.
  • ARM - ARM-based platforms (RISC OS, Acorn Archimedes, Gameboy Advance, etc.)
  • RISC-V - RISC−V micro-processors.
  • ReGIS - VT125, VT230, VT240/241 and more terminal display vector graphics language.
  • Bytebeat - Tiny music created from mathematical expressions.

By "very tiny programs", we usually mean programs that are 1024 bytes or less in size, typically created by members of the demoscene as a show of programming skill. In other scenes this artform is sometimes also known as generative , codeart , proceduralart , generativeart , codegolfing , codegolf , tweetcart dwitter , twigl and tweetjam.

The size of these tiny programs is measured by their total size in opcode bytes, and are usually presented as an executable binary. Despite their tiny size, these programs are able to produce amazing graphical displays, playable games, and sometimes music. There are even some surprisingly effective programs in just 16 bytes [1] or even 8 bytes [2].