How to Make and Share a Game with TIC-80

TIC-80 (tic80.com, currently v1.4.0) is a free and open source "fantasy computer" for making, playing, and sharing tiny retro games. You build everything inside one program using its built-in code, sprite, map, and sound editors plus a command line, and you finish with a cartridge file that can be stored and played on the website or packed into a standalone player for distribution. The catch is that all of this happens under fixed technical limits: a 240x136 pixel display, a 16-color palette, 256 8x8 color sprites, and 4-channel sound. If your idea fits inside those constraints, the whole loop from blank project to shareable game stays in one tool.

What you need before starting

• A copy of TIC-80 for your platform (the site presents it as free and open source; the page does not list pricing tiers or account requirements, so treat any login or download conditions as something to confirm on the site itself).
• A game concept small enough for the limits above. A single-screen arcade loop, a short platformer level, or a tiny puzzle fits naturally; a large open-world game does not.
• No external art or audio pipeline is strictly required, since the editors are built in. You can still import assets if you prefer, but the built-in tools are enough for a mini retro game.

The build workflow

The order below follows how the built-in tools relate to each other. Exact menu names and shortcuts are not documented on the page, so use the editor labels you see in your version.

1. Set up the project

Create a new cartridge. This is the file that will hold your code, sprites, map, and sound together, and it is also what you eventually share.

2. Draw sprites

Use the sprite editor to create your 8x8 tiles within the 16-color palette. Keep a consistent palette early; changing it later means reworking art. The 256-sprite budget is shared across everything in the game, so plan characters, tiles, and UI together.

3. Build the map

Place your sprites in the map editor to lay out levels or screens. Because the display is 240x136 pixels, think in screens rather than long scrolling vistas unless you build scrolling yourself.

4. Write the code

Use the code editor to script game logic: input, movement, collision, scoring, and screen transitions. Keep the loop simple and test often, since the small display makes problems visible quickly.

5. Add sound

Use the sound editor to create effects and music within the 4-channel limit. Four channels means you are budgeting, not layering freely: decide early which channels carry music and which carry effects.

6. Use the command line

The built-in command line handles project-level tasks such as running the game and managing the cartridge. Use it to test the full build rather than only previewing individual editors.

7. Verify before sharing

Run the game from start to a natural end point and check:

• Every screen fits within 240x136 and reads clearly at that size.
• Colors stay within the 16-color palette.
• Sprite and map usage stays inside the 256-sprite budget.
• Audio does not exceed 4 channels and does not cut out during busy moments.
• The game starts, plays, and ends without needing a restart.

Sharing your game

You have two routes, and they serve different audiences.

The website route is the shortest path: your cartridge can be stored and played directly on the site, which is also where the community's new and popular carts are showcased. The packed-player route takes more setup but lets you distribute the game as you wish on the platforms the player supports.

Common sticking points

• Running out of sprites. The 256-sprite limit includes tiles, characters, and UI. Reuse tiles aggressively and keep UI minimal.
• Audio dropping out. With only 4 channels, a music track plus several simultaneous effects will collide. Reserve channels or simplify effects.
• Text that is unreadable. At 240x136, small fonts blur. Design text at the pixel level rather than scaling it down.
• Scope creep. The limits are the point of the format. A finished small game shared on the site is worth more than an unfinished large one.

A realistic first project

Aim for something like a single-screen game where the player collects items while avoiding moving hazards, with one music loop and two sound effects. That exercises every editor, stays inside every limit, and produces a cartridge you can store on the website the same day. Once that ships, the packed-player route is a natural next step for distributing it more widely.