Pablo Murad

Software as culture: the demoscene

· 12 min read · #demoscene · #retro · #computers · #history · #programming

Contents

We have a slightly annoying habit of treating software as a tool and nothing else. One program edits photos, another does spreadsheets, another plays music, another runs a server. In that logic, good software is useful software: fast, secure and, with some luck, it won't ask you to create an account before showing you the main screen.

Computers were never only tools, though. As soon as they landed in the hands of curious people, somebody tried to find out what else they could do. There was no client waiting, no business problem, no investor asking for 30% growth next quarter. The motivation was often much simpler: "I want to see if this machine can do that."

That itch gave us one of my favorite subcultures in computing, the demoscene.

If you've never seen a demo, the first impression can fool you. It looks like a music video for some electronic track, or a 3D animation with a soundtrack. The file you run, though, is a program, and the computer is generating the graphics, the movement and the music in real time, while you watch. Assembly, one of the oldest parties of the Finnish scene, describes demos exactly like that: self-contained programs that produce audiovisual presentations as they run.

Any modern computer can render impressive things. What makes the scene special is that a big part of it grew around limits much tighter than "it has to run on a laptop with 8 GB of RAM": fitting a whole audiovisual piece into 64 KB. Or 4 KB. Or 1 KB.

There are people who look at a 4096-byte limit and decide there's room in there for a mountain range with a soundtrack. Those people are the reason I like computers.

A sports hall at the Breakpoint 2005 demoparty, packed with tables full of computers, CRT monitors and people, under a blue Intel banner.

Before demos, there were crackers #

The demoscene didn't start in art schools or university graphics labs. It started with software piracy in the 1980s, with the groups that stripped copy protection from games and programs for home computers.

When a group cracked a game, it was common to put a small intro in front of it. The intro showed the group's name, some messages and greetings to other crackers. As the competition grew, those intros got logos, music, scrolling text and graphic effects. People called them crack intros, or cracktros.

The groups started competing over who had the best intro, and not only over who cracked a game first. Effects got better, music got more important, coders started abusing tricks specific to each machine and, somewhere in the second half of the 1980s, that competition began to separate itself from cracking. Assembly's own history of the scene tells this move from cracktros to bigger and bigger productions.

I love this origin because it sounds like something the internet would make up later. Someone pirates a game and signs it. The signature gets boring, so they add music. A rival group answers with a better effect, another one adds animation, and before anyone notices, the game is the least interesting part of the package. Drop the game, keep the intro, and you have a new kind of digital culture.

Some habits from that period are still around. The scrolltext, that line of text sliding across the screen, became almost a signature of the scene, and there's research that follows it from the cracktros of 1984 to the much more elaborate demos that came after.

What does a demo demonstrate? #

The word can confuse people, because we're used to "demo" meaning a crippled version of a commercial program. You use it for fifteen minutes and then a BUY NOW button shows up.

In the demoscene, the demo is the finished work. What it demonstrates is how much its authors can squeeze out of the machine.

That changes how you watch these things. With a Commodore 64 demo, part of the fun is knowing that the image comes from a computer released in 1982, with 64 KB of RAM and a processor running at about 1 MHz.

A beige Commodore 64 home computer with its built-in keyboard, photographed on a white background.

Here programming and art start to blur. The hardware stops being a neutral platform and becomes part of the piece. Someone making a C64 demo knows the VIC-II and SID chips, the memory map, the graphics modes and the timing quirks of the machine. Someone coding for the Amiga knows its custom chips and spends an unreasonable amount of time finding rude ways to make them work harder. A lot of the fun is in behaviors the original engineers probably never imagined anyone would use for art.

That's why people still release new work for machines that died commercially decades ago. The Commodore 64, Amiga, Atari ST, ZX Spectrum and Amstrad CPC are still creative platforms. The German UNESCO commission lists size-coding, the craft of making programs absurdly small, as one of the core skills of the scene.

I find that relationship with a computer much more interesting than swapping the GPU every two years. The machine has a personality: flaws, limits, tricks, odd timings and things that "shouldn't work." Then someone makes them work.

64K, 4K and the art of having no room #

For me, the most impressive door into the scene is the size-limited intro. A 64K intro has to fit in 65,536 bytes. A 4K intro gets 4,096. Depending on the party there are categories for 1K, 256 bytes and other unreasonable sizes.

Nobody is cramming megabytes of textures into 4 KB with some secret ZIP format. The trick is to store ways of making things instead of the things themselves. A texture can be generated by math. A 3D object can be built from functions and geometric operations. The music comes from a tiny synthesizer running inside the program. Shaders draw images procedurally. Noise, fractals and formulas take the place of data that would fill huge files in a normal project.

There's something beautiful about this, because it goes against the grain of modern computing. Storage is cheap, RAM is plentiful and processors are monsters, so it feels normal to download hundreds of megabytes to install an app that shows a to-do list. The demoscene asks the opposite question: how much can you remove before the thing stops existing?

One production that mattered a lot here is fr-08: .the .product, by the German group Farbrausch. It won the PC 64K intro competition at The Party 2000, in Denmark, and became a reference for procedural content and real-time sound synthesis.

Then there's Elevated, by RGBA and TBC, released at Breakpoint 2009 in Germany. It shows a 3D mountain landscape with terrain, atmosphere, a moving camera and music, and it won the 4K competition. The whole thing is 4,096 bytes. That number should be printed on a sign at the door of every software company, just to cause a little collective embarrassment.

Nobody does this alone #

The scene is also very social. People organize themselves in demogroups, each with a name and members who do different jobs. The coder writes the program, the graphician handles the visuals and the musician writes the soundtrack. Bigger productions add modelers, designers and people who build tools, synths and shaders.

Almost everyone uses a nickname, called a handle, which is another inheritance from hacker and cracker culture. That's how names like Purple Motion, Skaven, Chaos, kb, ryg, Lone Starr and Travolta became recurring credits in classic productions. The groups built identities too: Future Crew, Spaceballs, Farbrausch, Kefrens, Conspiracy, Andromeda, Fairlight, Haujobb and dozens more.

There was no career waiting at the end. The prize was reputation. You made something that impressed other sceners, released it at a party, people voted, maybe you won, and your handle started to travel. It's a primitive version of online status, decades before likes and followers, with one difference I like a lot: you were showing off to people who knew exactly how hard the thing you did was.

The parties #

If the scene were only people mailing executables to each other, it would never have become what it is. The heart of it is the demoparty, a physical gathering where demos, intros, music and graphics compete in categories called compos.

Picture a LAN party that met a digital art festival, had a few beers with a hackerspace and decided to run a creative programming championship. That's roughly it. People bring their machines, spend days together, finish their entries at the last possible minute, watch everything on a big screen and vote. In between there's music, code, conversation, old hardware and, judging by forty years of photos, a fair amount of beer.

Assembly started in Finland in 1992 and became one of the pillars of the scene; its summer edition still happens every year in Helsinki. Denmark had The Party through the 1990s. Norway had The Gathering. Germany later gave us Breakpoint, Revision and Evoke. Evoke began in 1997 and has been held in Cologne since 2002.

None of this is archaeology. Demoparty.net keeps a calendar, and there's something happening in Europe almost every month. The people who made demos as teenagers in the 80s and 90s are now in their fifties, with kids, jobs and probably very detailed opinions about lower back pain. New people keep showing up anyway, and the old machines keep showing up on the tables.

Why Europe? #

The demoscene exists all over the world, but after a few minutes of reading about it you notice the strong European accent. Finland, Sweden, Norway and Denmark had huge scenes. Germany is a historic powerhouse. Poland has an important community, and so do the Netherlands, France and several countries in Central and Eastern Europe.

There are good historical reasons. Home computers like the Commodore 64, the Amiga and the Atari ST built strong communities in those countries in the 80s and 90s. Before the internet, software, demos and messages traveled on floppy disks, by mail, through BBSes and at meetings. The scene had its own social networks before we called everything a social network.

That world fed the European game industry later on. Remedy Entertainment, for example, talks openly about its roots in the Finnish demoscene. It makes sense: if you spent your teens making a PC or an Amiga draw impossible graphics in real time, working with graphics and games is a natural next step.

A few things to watch #

Any list here is unfair, since we're talking about decades of work on dozens of platforms. Still, some demos come up so often that they work as a way in.

Second Reality, by Future Crew, is the classic. It won the PC demo competition at Assembly 1993 and became one of the best-known productions in the scene's history. It's pure DOS, proudly 1993 in its looks, and a lesson in what people could do with hardware that would embarrass a supermarket calculator today.

On the Amiga, State of the Art, by Spaceballs, won at The Party 1992. It's very different from Second Reality: instead of a parade of technical effects, it works with dancing human silhouettes, fast cuts and music. It still has a strong visual personality.

After those, I'd go to Desert Dream by Kefrens, then fr-08 and Elevated. I wouldn't treat this as a top five. The fun is to start with a few landmarks and then lose control completely. There's a real chance you'll put on Second Reality at eleven at night and, by two in the morning, be downloading some Atari Falcon intro from 1996 made by someone with a ridiculous handle.

Where the scene keeps its memory #

One of the best things this community did was keep records. Many of its sites look like they survived from a web that never heard of design systems, conversion funnels or "Start for free" buttons, which makes me feel right at home. If I were starting today, I'd open these:

  • Pouët: the town square. Productions, comments, ratings, screenshots and decades of arguments between sceners. Sometimes a historic masterpiece sits right above a comment that just says "boring."
  • Demozoo: probably the best place to research the history. It catalogs demos, groups, people, platforms, parties, results and credits. The amount of information is absurd.
  • Scene.org: a big piece of community infrastructure, with a huge file archive of the scene.
  • Demoparty.net: the event calendar, and the best way to find out there's an obscure party next month in a Finnish town you've never heard of.
  • CSDb: the Commodore 64 Scene Database, the specific rabbit hole for anyone developing an unhealthy fixation on the C64.
  • Hornet Archive: a huge part of the PC scene from 1987 to 1998. For the DOS era, it's a time capsule.

These sites show something I think matters: the scene was never only about consuming digital art. There's an obsessive record of who made what, in which group, at which party, what place it got and which machine it ran on. Authorship matters a lot there. Maybe because when a 4 KB program does something that looks impossible, the first natural reaction is to ask who the lunatic behind it was.

And Brazil? #

Brazil has a demoscene, but nothing close to the size of Finland's, Germany's or Poland's. There are Brazilian groups and productions going back to the 1990s, but parties were rare. A good example is Art Engine 2012, held in São Paulo from February 3 to 5, 2012, with competitions for demos, game development, graphics, music and wild entries. According to Demozoo, it was the first demoparty in Brazil in fifteen years.

That says a lot about the size of our scene. Fifteen years between two parties isn't exactly a busy calendar. In Latin America, Argentina has been more visible, mostly thanks to Flashparty.

It has always puzzled me that Brazil never grew a bigger scene. We have a history with computers, electronic music, piracy, BBS culture, hacking, free software, digital art and plenty of people who take things apart just to see how they work. The ingredients were here. My guess is that we lacked a strong tradition of parties to turn scattered individuals into a scene. A subculture doesn't appear just because people like the same thing. They have to meet.

From pirated floppies to cultural heritage #

My favorite plot twist in this story is recent. Several European countries now recognize the demoscene as intangible cultural heritage. Finland went first, in 2020. Germany and Poland followed in 2021, then Switzerland and the Netherlands, Sweden and France in 2025, and in April 2026 Norway became the eighth country on the list.

It's worth being precise here, because this gets oversimplified a lot. UNESCO didn't declare the demoscene a World Heritage Site, as if it were the Acropolis or the old center of Ouro Preto. These are national inventories of intangible cultural heritage, which follow the principles of the UNESCO convention. The Art of Coding initiative, launched in 2019, has been pushing for this recognition country by country.

Even with that footnote, the arc is wonderful. In the 1980s, teenagers were modifying pirated games and putting their nicknames in front of them. Forty years later, European governments are discussing how to preserve what those teenagers started. I doubt anyone making the first cracktros had that plan.

Software can be culture too #

This is probably what interests me most about the demoscene. We're surrounded by software and we almost never think of it as a form of cultural expression. We call cinema, music, architecture and photography art, while programs are still treated mostly as commercial tools.

The scene doesn't accept that split. There, the code is part of the work. How a program pushes a specific machine, generates an image or works around a limit is part of the experience, just like the music and the visuals. That's also why watching a recording of a demo and running the real thing aren't the same. The video shows you the result, while the executable shows you the whole idea.

I like knowing that a file holds enough instructions to turn silicon into image and sound, and that someone spent nights trying to shave off twenty more bytes because the thing was too big for the compo.

I don't think the lesson is that all software should be 4 KB. That would be a pretty dumb conclusion. What I take from it is that limits can create a language, and that knowing a tool deeply lets you use it in ways its makers never imagined. Programming doesn't have to exist only to automate a company, sell a subscription, serve ads or close a Jira ticket. Sometimes you write code because you want to make something beautiful, or strange, or technically absurd, or because you want to see how far a machine can go.

After forty years, this culture still looks at a computer and asks the simplest question there is: can it be done? Bad luck for the computer when the first answer is no.

Sources #