What Is the Demoscene and How Can You Get Started?
The demoscene is a digital art subculture that began in the 1980s, when software crackers started adding flashy audiovisual intros to their releases. Those intros grew into standalone "demos"—real-time, self-contained programs that generate music and graphics on the fly rather than playing back video files. You can get started by watching classic demos on portals like Pouet, attending or following events such as Revision, and then trying your hand at a small production with tools like a tracker for music and a shader or framework for visuals. The scene is open to newcomers, but the most rewarding entry point is making something and releasing it, not just consuming.
What Makes a Demo Different From a Video
A demo is a program, not a recording. Everything you see and hear is computed in real time on the target machine, which is why demos are often used as informal benchmarks and why size limits matter so much.
That constraint drives the scene's signature categories:
- Demo – the main form, usually with no strict size limit, often several minutes long.
- Intro – a short demo, historically 64 KB or smaller, sometimes just a few seconds.
- 4K / 64K / 256K – competitions where the entire executable must fit in that many bytes.
- Wild / wild demo – entries that use unusual hardware or non-standard platforms.
Because the code must fit in a tiny budget, demosceners develop deep tricks: procedural texture generation, self-modifying code, compression, and hand-tuned math. This is the same skill set that shows up in game development, graphics programming, and retro computing.
How the Scene Is Organized
The demoscene is not a company or a platform. It is a loose network of groups, events, and archives.
| Element | What it is | Where to find it |
|---|---|---|
| Groups | Teams that co-create demos, often with coders, musicians, and graphicians | Listed on Pouet and scene.org |
| Parties | Physical gatherings with competitions, seminars, and socializing | Revision, Assembly, Evoke, and many local events |
| Portals | Archives and databases of releases, ratings, and comments | Pouet, scene.org |
| Tools | Trackers, frameworks, and engines used to build demos | Open-source and freeware tools |
Geeks3D, a site covering 3D tech news, graphics cards, programming, and gamedev, lists demoscene among its topics and has covered events such as Revision 2026. That is a useful signal: the scene overlaps heavily with graphics programming and hardware news, so following a site like Geeks3D can keep you aware of both driver updates and scene activity.
How to Start Watching and Learning
You do not need to write code to begin. Start by watching.
- Pick a portal. Go to Pouet and browse the top-rated demos. Filter by platform or year if you want a specific era.
- Watch a few classics. Look for well-known releases from the 1990s and 2000s, then compare them with modern 4K intros. The contrast teaches you what the constraints actually mean.
- Read the comments. Pouet entries often include technical discussion and links to source code or explanations.
- Follow a party. Revision is one of the largest demoscene events and is a good entry point for streams and competition results. Geeks3D's coverage of Revision 2026 is an example of how the scene appears in general tech news.
- Join a community. Discord servers, IRC channels, and party forums are where beginners ask questions and find collaborators.
How to Start Making Something
The first step is to choose a constraint. A 4K intro is a common beginner target because it forces you to focus on a single effect and a short piece of music.
A practical path:
- Music: Learn a tracker such as OpenMPT or Renoise. Trackers are the traditional demoscene music tool and produce small module files.
- Graphics: Start with a shader environment like Shadertoy to practice procedural visuals, then move to a framework such as OpenFrameworks, Processing, or a custom OpenGL/Vulkan setup.
- Packaging: Use a size-limited intro framework or a cruncher to fit your executable into 4K or 64K.
- Release: Upload your production to Pouet and submit it to a party competition. Feedback is part of the culture.
If you already make games, the transition is natural: demos are essentially real-time graphics and audio with no gameplay layer, so the same engine skills apply.
Common Questions and Pitfalls
Do I need to be a programmer? No. Musicians and graphicians are core members of demo groups. Many groups recruit for all three roles.
Is the scene only for old hardware? No. Modern demos target current GPUs and APIs, including OpenGL and Vulkan. Retro platforms are one branch, not the whole scene.
Do I have to attend a party in person? No. Many parties stream competitions and accept remote entries. Attending in person is a social accelerator, not a requirement.
What is the biggest mistake beginners make? Trying to build a full demo first. Start with a 4K intro or a single effect, release it, and iterate.
Where do I find source code? Many demoscene releases include source or are open source. Pouet entries and scene.org archives are the places to look.
Where This Connects to the Rest of Tech
The demoscene sits at the intersection of graphics programming, game development, and retro computing. The techniques developed under size constraints—procedural generation, compression, real-time audio synthesis—show up in game engines, shader work, and embedded systems. Following demoscene news alongside general 3D and GPU news, as Geeks3D does, is a reasonable way to stay connected to both. If you want a concrete next step, watch three top-rated 4K intros on Pouet, pick one effect you like, and try to reproduce it in a shader environment.