TL;DR / Summary: Game-jam menus need a loop that feels finished in under an hour of audio work. A tight Sprunki bed—few characters, clear downbeat, no surprise drops—gives players something pleasant to sit in while they poke options, without stealing focus from your UI.
Menu music is furniture, not a boss fight
Title-screen audio fails in two opposite ways: it is so thin that silence would have been kinder, or so busy that players mute the game before the first level. Menu loops should occupy the middle: rhythmic enough to feel alive, sparse enough that button clicks still cut through.
Sprunki’s character stacking makes that middle reachable quickly. You hear arrangement decisions in real time instead of exporting twenty Ableton bounces.
Start with pulse, then add colour
Lock a steady percussion character first. If the groove wanders, every later layer will sound late even when it is on grid.
Add one tonal bed next—chords or a soft arp—before any lead. Leads scream “level music.” Beds say “you can linger here.”
A jam-friendly layer order
- Percussion: simple, loop-length clear
- Bass or low pulse: defines key without melodic ambition
- Pad or chords: warmth for idle time
- Optional ear candy: one motif every eight bars, not every two
Stop at three or four voices. Menu screens are where players adjust volume; dense mixes get turned down permanently.
Loop points players do not notice
The cruel test: leave the menu open for three minutes while you fix a bug. If you can hear the seam each cycle, the loop is not ready.
Prefer patterns that resolve on the same beat they begin. Avoid endings that feel like a chorus stop, then restart. A soft sustain across the join hides more sins than a dramatic fill.
If you flinch at the loop join, players will mute you by minute two.
Export a longer take than you need, then trim in your engine to the cleanest bar line. Engines forgive uneven file length; ears do not forgive uneven phrasing.
Matching UI energy without matching genre stereotypes
A puzzle game does not require music-box clichés. A racing jam does not require distorted guitars. Match energy: calm UI, calmer bed; frantic prototype, slightly brighter percussion.
Colour palette and music should agree. Dark UI with sunny major loops feels accidental. You can keep Sprunki playful and still choose darker voicings.
Try the loop against your actual button sounds. If both occupy the same midrange, duck the music a touch or thin the percussion.
Licensing and attribution under jam deadlines
Know what your jam allows before you ship. Some events want original audio only; others allow tools and require credits. Put the tool and your arrangement note in the readme while you still remember what you did.
Record your own take rather than assuming a browser session is a deliverable. Capture clean audio from the session you liked, then bounce a WAV for the build.
Build the bed in Incredibox Sprunki, commit the export to your jam repo, and move on. Perfect is the enemy of submitted.
Volume, buses, and the mute button
Expose a music slider separate from SFX. Menu loops are the first thing players negotiate with roommates and late-night headphones.
Start music a few decibels quieter than you enjoy in solo testing. Fatigue sets in for anyone who leaves the title screen open while reading patch notes.
Fade in over half a second on first boot. Hard starts feel like errors.
File formats engines actually swallow
Export WAV for the master, then compress to OGG or the format your engine prefers for shipping size. Keep the WAV in the repo even if the build uses a smaller file; re-bouncing from a lost browser session mid-deadline is avoidable pain.
Name files with tempo and key in the filename: menu_96bpm_a_min.ogg. Future you will not remember which sunny loop was the finalist.
Test the loop inside a build, not only in headphones on the arrangement tab. Engine latency and mobile speakers change how busy a bed feels.
Options screen and credits as cousins of the menu
You can reuse the same bed under options and credits if you duck it slightly and remove the ear-candy motif. Players perceive continuity without thinking the game has only one song.
If credits need a tiny lift, add one extra character for that scene alone and keep the menu version thinner. Two related exports beat one loud file everywhere.
Never let credits music restart aggressively each time the player reopens the screen. Respect the loop point you already fought for.
When to retire the menu loop
After the jam, you may replace the bed with a custom track. Keep the Sprunki export anyway. It documents tempo, key, and mood decisions that a new composer can match.
If players compliment the menu music in comments, consider expanding that bed into a short level variant instead of inventing a second identity from scratch.
A loved menu loop is a prototype of your game’s emotional pitch.
Ship the calm loop, protect the UI, and save heroic drops for gameplay. The menu’s job is to make waiting feel intentional.


