Musicians can sell custom game and app background loops by scoping a made-to-order custom request — a short, seamless instrumental track built to the developer's length, mood, and loop-point spec — and pricing it directly from a bio link instead of a freelance marketplace listing or an unpriced DM thread. Custom Work lets you offer clearly scoped commissions and services: you set the price, the scope and the delivery time, and followers submit a brief and pay before you start.
Followers pay upfront by card as guests before you start, and you deliver later. Brillay has an 8% platform fee when a follower pays for work and 5% on tips and goals (Brillay — Pricing).
A game or app background loop is different from a finished song: it is a short instrumental cue — a menu screen, a level, a puzzle, a checkout flow, a loading state — built to repeat cleanly without a jarring restart. How often developers ask musicians for one is not a figure any platform publishes, so treat "devs ask constantly" as anecdote; what is measurable is the number of products shipping that need short repeating audio, and the per-minute rates composers report charging for indie work.
| Request | Better-fit format | Why |
|---|---|---|
| One short quote on a loop concept before committing | Paid Questions | The developer just wants feedback in text before paying for a full track |
| A finished, seamless loop delivered as a file | custom request | The deliverable is an audio file with a set price and delivery time |
| Ongoing music for a game across multiple builds | Separate, larger engagement | A single loop offer should not expand into an open-ended scoring contract |
| Support from a follower who likes your game-audio work | Tips | A supporter sends a one-time amount to say thank you |
Why do indie developers need custom background loops?
Indie developers commission custom loops because a stock library track rarely matches one screen's tempo, mood, and loop length, and a small team's budget rarely stretches to an in-house composer. A 30-second menu cue is small, well-defined, fixed-price work for a musician and a purpose-fitted asset for the developer — bought once, dropped straight into the build.
SteamDB's Steam Game Release Summary counts 21,320 games released on Steam during 2025 (SteamDB). The same SteamDB summary filtered to Steam's "Indie" tag counts 10,784 of those 2025 releases (SteamDB). Apple's 2024 App Store Transparency Report lists the total number of apps on the App Store as 1,961,596 (Apple). A store tag is not a team-size measure, and neither Valve nor Apple publishes how many releases come from one- or two-person teams, so any "solo dev" count is inference rather than measurement.
What is measured is the price tier. GameSoundCon's 2025 Game Audio Industry Survey, which collected 654 responses between May 1 and June 15, 2025, reports that among freelance composers charging by the minute for indie games the most common rate was $400 per minute of finished music, with an average of $618 and a median of $407 (GameSoundCon). The same 2025 GameSoundCon survey reports AAA freelance rates clustering at $1,000, $2,000, and $3,600 per minute of finished music, averaging $1,871 — a different market from a single 30-second menu loop.
GameSoundCon has tracked outsourced game audio as a share of game-audio employment every year since 2016:
"The percentage of people employed by audio outsourcing companies has steadily increased, almost tripling from 5% of people working in game audio in 2016 to 14.7% in 2025." — GameSoundCon, 2025 Game Audio Industry Survey
A musician who already posts game-adjacent content — chiptune covers, DAW breakdowns, remix streams — is a lower-friction alternative to a cold marketplace search for developers looking outside their own team for audio.
Paid Question or custom request — which fits a loop request?
A loop request should go through Custom Work because the deliverable is an audio file. Paid Questions on Brillay are answered in writing; Custom Work carries a price and a delivery time, and its delivery is text plus files and/or a link.
Brillay's Custom Work page describes a service delivery as "a written note plus up to 5 files (video, audio, images, PDF, Word, Excel, or PowerPoint), and/or a private link… for anything larger," with video or audio capped at 20 minutes per file (Brillay — Custom Work). A 30-to-90-second loop plus a stems folder therefore fits comfortably inside one five-file delivery, and an uncompressed multi-track session that exceeds the file limit goes to the follower as a private link instead. Paid Questions are one typed question and one written reply (Brillay — How It Works).
Use Paid Questions only for the step before the sale: a developer asking "can you do something upbeat and 8-bit for a shop screen?" and wanting a quick written yes/no plus rough scope before committing. Once the answer is yes, sell the loop itself through Custom Work with a set price and delivery time.
Choose a delivery time you can meet; you deliver Custom Work within the time you set, up to 5 days. Brillay's delivery-time setting for a custom request is a creator-set value capped at up to 5 days, per order, and delivery itself happens asynchronously, on your own time within that window, with no live call or appointment to schedule. A 5-day ceiling fits one short loop well and rules out selling an entire game's score as a single listing.
What should a background-loop listing include?
A background-loop listing should specify the exact deliverable before payment rather than advertising "custom game music," so the developer knows what they are buying and the composer knows what is owed. Six fields — length, loop points, file format, mood reference, revision policy, and usage scope — take one line each and cover the terms that otherwise surface as disputes after delivery.
- Length: a fixed figure such as a 30-second or 60-second loop, rather than an open-ended track.
- Loop points: whether the file is a seamless loop-ready bounce or a straight linear cue the developer loops in-engine.
- File format: which files ship — for example a 44.1 kHz/24-bit WAV plus an MP3 reference — and whether stems are included.
- Mood/reference: the developer's one-line brief (menu, boss fight, calm exploration) plus any reference track.
- Revision limit: a stated policy — zero, one, or two rounds — written into the description before anyone pays, so a post-delivery correction request has clear terms to follow.
- Usage scope: which project or projects the file may be used in, and whether the license is exclusive.
With Custom Work, define the finished files before payment and deliver once; after delivery, the follower can open a support conversation on that same order for a correction under the policy you stated in the listing, and a request that goes beyond the original scope becomes a new order instead. Followers pay upfront; you can decline a request.
What do concrete loop packages look like?
Three tiers cover the request shapes that arrive most often: a single short loop, a small pack for a whole build, and an exclusive buyout. The prices, deliverables, and delivery times in the table below are illustrative examples — not Brillay defaults, industry benchmarks, or measured averages — and the offer details are set by the creator.
| Illustrative package | Scope | Example price | Revision policy | Delivery | delivery time |
|---|---|---|---|---|---|
| Single menu loop | One 30-second seamless loop, non-exclusive, one named project | $75 | 1 stated round | WAV + MP3 | 72 hours |
| Build pack | Three 60-second loops (menu, level, victory), non-exclusive, one named project | $250 | 1 stated round per loop | WAV + MP3 + stems | up to 5 days |
| Exclusive buyout | One 60-second loop, exclusive use, composer does not resell | $400 | 2 stated rounds | WAV + MP3 + stems | up to 5 days |
All three illustrative delivery times — 72 hours and up to 5 days — fit within Brillay's 5-day per-order delivery cap. On a $250 Custom Work order, Brillay's 8% platform fee is $20.00; tips and goals carry a 5% fee instead. Stripe's published rate for US domestic online card payments is 2.9% + $0.30 per successful transaction (Stripe), which is $7.55 on a $250 order — leaving roughly $222.45 to the composer before their own taxes.
How should licensing and usage rights be defined?
Licensing should be defined as a plain-language usage scope written inside the listing: the creator states what the follower may and may not do with the delivered file. The practical choice is a non-exclusive license, which lets the composer resell the loop, or an exclusive buyout priced higher.
With Custom Work, you write what the follower gets, the price, the delivery time, and the usage scope in the description.
The exclusive-versus-non-exclusive distinction has a specific legal shape in the United States. Section 101 of the US Copyright Act defines a "transfer of copyright ownership" as "an assignment, mortgage, exclusive license, or any other conveyance.. but not including a nonexclusive license" (U.S. Copyright Office, Title 17 § 101), and Section 204(a) states that such a transfer "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed" (U.S. Copyright Office, Title 17 § 204(a)). An exclusive deal therefore needs a signed writing to be valid under US law, while a non-exclusive license does not — general information, not legal advice, and non-US creators should check their own jurisdiction's rules.
Licensing rather than transferring is already the more common indie arrangement: GameSoundCon's 2025 Game Audio Industry Survey found that 36% of freelance composers licensed their music to the developer or publisher on their last indie game, versus 11% on mid-core games and 0% among the AAA freelancers surveyed.
The alternative a developer weighs against a commission is a stock-music subscription. Epidemic Sound's own plans page lists a Creator plan at $9.99 per month billed annually ($119.99 a year), or $203.88 a year billed monthly (Epidemic Sound). With Brillay Custom Work, a commissioned loop competes on fit and exclusivity rather than on price per track because it is made for one developer’s screen, timing, and brief rather than pulled from a catalogue where every buyer gets the same track, which is why usage scope belongs in writing: "one indie title, unlimited builds, non-exclusive" reads very differently from "exclusive, all platforms."
How do you avoid Content ID problems for streamed or Let's Played games?
Avoid Content ID problems by delivering only original audio you fully control, stating in the listing that the loop contains no third-party samples or stock-library material, and agreeing with the developer on who — if anyone — registers the track with a content-matching service. YouTube matches uploaded audio against a rights-holder database regardless of who composed a track.
Google's YouTube Copyright Transparency Report states that of the 2 billion-plus Content ID claims made in 2025, fewer than 1% were disputed, and that over 65% of those disputes resolved in favor of the uploader (Google). Because fewer than 1% of Content ID claims are disputed at all, the practical default after a match is that the claim stands and the video's revenue routes to whoever registered the audio.
"Using a database of audio and visual files submitted by copyright owners, Content ID identifies matches of copyright-protected content." — YouTube Help, How Content ID works
If a developer's game is streamed or uploaded by players and the delivered loop is registered elsewhere — in a sample library or on a stock site — under different terms, a Content ID claim can land on the developer's or a streamer's video even though the developer paid the composer directly. Stating in the listing that the delivered file is an original, cleared composition rather than a build from a sampled loop the composer cannot redistribute removes that downstream risk before it reaches the buyer.
What else can musicians sell around game and app audio?
A background loop does not have to be the only paid offer on a music page. Adjacent formats capture the requests that arrive alongside loop commissions — quick production questions, trailer beats, support from viewers — without letting every conversation expand into a full scoring job. Five formats cover most of that surface area.
- custom request variants: Twitch stream intro music for the same developer's own channel, or a custom beat for a trailer.
- Paid Questions: quick production or mixing questions from developers doing their own audio.
- Tips: support from viewers who enjoy your game-audio content but aren't commissioning anything.
- Goals: funding toward a sample pack, plugin, or gear upgrade tied to your game-audio work.
- Brand Collaboration Inquiries: a separate inbox for studios or audio-middleware companies proposing an ongoing partnership rather than a one-off loop.
Mixed income is the norm in this field: GameSoundCon's 2025 Game Audio Industry Survey reports that game-audio freelancers make on average 67% of their income creating game audio, with another 15% coming from audio work outside games. Pricing a full commission separately, using a framework like how much to charge for beats, keeps a quick loop offer from being confused with a larger licensing deal.
How do you get a background-loop offer live on Brillay?
Getting a loop offer live takes four steps: choose Custom Work, write the six scope fields (length, loop points, file format, mood reference, revision policy, usage scope), set a price and a delivery time, and publish the listing. No application queue or audience threshold stands in the way.
There is no follower minimum or application: put Custom Work, Paid Questions, and Tips on one Brillay link, and connect your bank through Stripe in any of 41 payout countries. Setup itself is described as a few minutes' work — claim the link, turn on a couple of offers, paste the link into a bio.
From there, route developers who DM "can you make us a loop?" straight to the link instead of negotiating price in a comment thread. Keep the first offer narrow — one loop, one length, one license scope — and add variants once you know what followers actually ask for.
Frequently asked questions
Should a game/app loop be a custom request or a Paid Question?
Use Custom Work, since the deliverable is an audio file: delivery includes "a written note plus up to 5 files (video, audio, images, PDF, Word, Excel, or PowerPoint), and/or a private link… for anything larger", while Paid Questions are one typed question and one written reply. Paid Questions still work as a pre-sale scoping step.
How long can I set the delivery time on a loop commission?
You set the delivery time from 1 hour to 5 days, depending on how long the loop will take you to finish. Anything longer than a 5-day promise needs to be scoped as a separate engagement outside a single listing.
Do I need to sign a formal license agreement with the developer?
On Brillay, you write the usage scope directly in the listing description. Under US law, an exclusive license is a transfer of copyright ownership and "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner of the rights conveyed" (U.S. Copyright Office) — so an exclusive deal warrants a signed written agreement, and a lawyer, rather than a listing line alone.
What if a developer wants a full soundtrack instead of one loop?
Decline and refund a request that goes beyond the listed scope, or redirect the buyer to a larger, separately priced engagement before starting. Custom Work works best when each offer is scoped to one loop or a small, defined pack.
What does Brillay charge on a sale like this?
On a $75 loop sale the Brillay fee is $6.00, and Stripe's published US domestic online card rate of 2.9% + $0.30 is $2.48 — leaving about $66.52 to the composer before taxes.
Can I sell the same loop to more than one developer?
Whether the same loop can be sold twice depends entirely on the license scope written into the listing. A non-exclusive license lets the composer resell or reuse the same loop elsewhere; an exclusive or buyout license does not. State which of the two is being sold in the listing itself so there is no ambiguity after delivery.
Create your free Brillay page and turn the next "can you make us a loop?" DM into a priced, scoped offer.
Keep reading
New in the library
Ready to get paid for the interactions you already get?
Create your free Brillay link