Advertisement
Sound Design Guides

How to Create and Sell Blip Sound Packs on itch.io: A Practical Guide

A practical, numbers-first guide to packaging and selling a blip sound pack on itch.io, covering revenue share, the pricing bands that actually sell, the file and license structure buyers expect, and the tag strategy that puts the pack on the right shelf.

A blip sound pack is one of the smallest products a sound designer can sell. It is also one of the easiest to underprice and under-package. Most blip packs on itch.io are a ZIP file of unnamed WAVs, a one-line description, and a price that was set by guesswork. The packs that actually sell are the ones where every element — the file structure, the license, the page copy, the tags, the price — has been decided deliberately rather than left to whatever felt right at upload time.

This guide is about those decisions. It assumes the blips themselves are already designed, using the parameters in the blip sound design guide or the square-wave synthesis guide. What it covers is the packaging and the selling: the revenue math, the price bands, the file structure a buyer expects, the license that prevents refund requests, and the tag strategy that determines whether the pack is ever seen.

What does itch.io actually take from a sound pack sale?

itch.io uses an open revenue sharing model. The seller chooses what percentage of each sale goes to the platform, from 0 to 100 percent. The default is 10 percent, but it is a slider in the seller settings, not a fixed fee. The platform does not take a hidden cut on top of that.

There is, however, a payment processing fee that is not optional and not controlled by the seller. For both PayPal and Stripe, the fee is roughly 2.9 percent plus $0.30 per transaction. This fee is applied to every sale regardless of the revenue share setting, and it is deducted before the seller's payout.

The interaction between the fixed fee and the pack price is the part most sellers miss. The $0.30 is a fixed cost, so it consumes a larger percentage of a cheap product than of an expensive one. At a $3 sale, the processing fee alone is about 13 percent of the transaction. At a $10 sale, the same fee is about 6 percent.

Sale price Processing fee Fee as % of sale Net at 10% platform share
$3.00 $0.30 + $0.087 = $0.387 12.9% $2.31
$5.00 $0.30 + $0.145 = $0.445 8.9% $4.01
$10.00 $0.30 + $0.29 = $0.59 5.9% $8.41
$15.00 $0.30 + $0.435 = $0.735 4.9% $12.77

The practical consequence is that a $3 pack and a $5 pack are not that far apart in net revenue. The $3 pack returns $2.31 and the $5 pack returns $4.01, which is a 74 percent increase in net for a 67 percent increase in price. The fixed processing fee is what makes the cheaper price less efficient.

The freelance pricing guide covers the pricing of custom audio work. A sound pack is a different product — it is sold many times at a low price rather than once at a high price — but the same principle applies: the price should be set so that the fixed costs (in this case, processing fees) do not eat a disproportionate share of the revenue.

What price bands actually work for a blip pack?

The price bands that sell on itch.io are narrower than the price bands for other game assets. Sound effect packs commonly sit between $2.99 and $19.99, with music packs slightly higher at $4.99 to $29.99[reference:2]. A blip pack is at the smaller end of that range, because the product is smaller: a few dozen short sounds rather than a comprehensive library.

Pack scope Price band What justifies the price
20–40 blips, one style $2.99–$4.99 Clean set, clear use case
40–80 blips, multiple categories $4.99–$7.99 Coverage, consistent naming, manifest
80–150 blips, organized set $7.99–$12.99 Full UI sound set, license clarity
150+ blips, multiple styles $12.99–$19.99 Comprehensive library, long-term value

The $2.99 to $4.99 band is the most crowded, and it is where most first-time sellers start. The problem with that band is that the processing fee consumes a larger share, and the perceived value of the pack is low. A seller who has 40 blips and prices at $2.99 is earning about $2.30 after fees, which means they need to sell roughly twice as many copies to earn the same amount as a seller with 60 blips priced at $5.99.

The price that works best for a blip pack is the one that matches the perceived scope. A pack of 60 well-organized blips with a clear license and a CSV manifest is worth $5.99 to $7.99, because the buyer is not just buying the sounds — they are buying the organization, the documentation, and the certainty that the license allows commercial use. A pack of 20 unnamed WAVs is worth $2.99 at most, because the buyer is doing most of the work themselves.

The pay-what-you-want model is available on itch.io and is worth considering for a first pack. It lets the buyer pay above the minimum, and it removes the friction of a fixed price for a buyer who is unsure about the quality. The suggested price should be set near the top of the band the pack belongs to, so that the buyer has an anchor for what the pack is worth[reference:3]. A blip pack with a $3 minimum and a $6 suggested price will earn more per sale than the same pack with a fixed $3 price, because some buyers will pay the suggested amount.

What does a buyer actually expect inside the ZIP?

A buyer who purchases a sound pack expects to open the ZIP and immediately understand what they have. The packs that fail this expectation are the ones that contain a folder of files named blip_01.wav, blip_02.wav, and a license text that says nothing about whether commercial use is allowed.

The structure that works is a versioned ZIP with four components: the sounds themselves, a start-here guide, a license, and a searchable manifest[reference:4]. The manifest is the part most sellers skip, and it is the part that makes the pack feel professional.

Component Format Purpose
Sounds WAV, 44.1 or 48 kHz, 16-bit The product itself
Start-here guide README.txt or PDF What the pack is, how to use it
License LICENSE.txt What the buyer may and may not do
Manifest CSV Filename, description, duration, channels, rate, depth

The manifest should include a row for every sound, with columns for the filename, a one-line description, the duration, the channel count, the sample rate, and the bit depth. The CSV format is deliberate: it opens in any spreadsheet, it is searchable, and it does not depend on the buyer having a specific audio application installed[reference:5]. A buyer who is integrating 60 blips into a game can filter the manifest by duration or description in seconds, which is a small convenience that makes the pack feel considered.

The filenames themselves should follow a consistent pattern. The Universal Category System (UCS) provides a public-domain framework for sound effect naming, with a structure like CATID_Source_Action_Perspective_Variation.wav[reference:6]. A blip pack does not need the full UCS structure, but the principle applies: the filename should be readable outside its folder. A file named UI_Click_Soft_01.wav is more useful than a file named blip_04.wav, because the buyer can search for it later.

The sounds themselves should be edited before they are packaged. This means trimming silence at the start and end, normalizing to a consistent peak level, and removing any unusable takes. The file size reduction guide covers the normalization and trimming process; for a pack, the goal is consistency across the set rather than maximum compression.

What should the license actually say?

The license is the part of the pack that determines whether a buyer can use the sounds in a commercial game, whether they need to credit the seller, and whether they can redistribute the sounds. A pack with a vague license will generate refund requests and support questions. A pack with a clear license will not.

The license does not need to be long. It needs to answer four questions explicitly.

Question Typical answer
Can the buyer use the sounds in commercial projects? Yes, unlimited commercial projects
Does the buyer need to credit the seller? No attribution required
Can the buyer redistribute the raw sounds? No, the sounds may not be resold or shared as standalone assets
Can the buyer use the sounds in a competing sound pack? No, the sounds may not be repackaged or included in another asset pack

The redistribution clause is the one that matters most for a sound pack. The buyer is purchasing the right to use the sounds in their own products, not the right to become a reseller of the same sounds. A license that explicitly prohibits redistribution prevents the situation where the pack appears in another asset store under a different name.

The license should be included in the ZIP as a separate text file, and a short summary should appear on the itch.io page itself. Buyers often check the license before purchasing, and a clear summary on the page reduces the number of questions before the sale[reference:7]. The legal sound sources guide covers the broader licensing landscape; a seller's license is the mirror image of that — it defines what the seller is granting rather than what the seller is allowed to use.

Why do tags matter more than the description for discoverability?

itch.io's browse pages are organized by tags. Every tag the seller sets is a shelf the pack appears on, and each shelf has a Popular listing and a Newest listing. The Popular listing is dominated by established packs; the Newest listing is where a new pack has a realistic chance of being seen.

The tag field is therefore the highest-leverage single edit on the page. The tags should describe what the pack actually contains, using the words a buyer would type into a search box. For a blip pack, the useful tags are the concrete requirements rather than the mood: sound-effects, sfx, ui, retro, 8-bit, audio, game-assets, and the engine the sounds are formatted for if that is relevant.

Tag What it puts the pack in front of
sound-effects Buyers browsing the sound effects category
sfx Buyers searching the common abbreviation
ui Developers specifically looking for interface audio
retro / 8-bit Developers building retro-style games
game-assets The broader asset browse page
audio Buyers browsing all audio assets

The title is the other high-leverage field, because itch.io's search engine is optimized for direct title search[reference:10]. A title that includes the literal words a buyer would search for — "Blip Sound Pack," "UI Sound Effects," "Retro Blips" — will appear in more search results than a title that is clever but not descriptive.

The description matters less for discoverability and more for conversion. Once a buyer has found the pack, the description needs to answer three questions in the first few lines: what is in the pack, how many sounds and what format, and what the license allows. A description that leads with a one-line summary and follows with a compact feature list converts better than a long paragraph that the buyer has to parse[reference:11].

The cover image is the visual equivalent of the title. It needs to work at thumbnail size, because that is how it appears in browse pages and search results. The standard size is 630 × 500 pixels, and the image should be legible at half that size[reference:12]. A pack with a clear cover image is more likely to be clicked than a pack with a screenshot of a waveform.

What does the first sale actually depend on?

The first sale depends less on the pack and more on the traffic. itch.io does not actively promote new asset packs in the way it promotes games in jams. The platform provides the shelf; the seller has to bring the buyer to it.

The traffic sources that work for a blip pack are the ones where developers are already looking for audio. A devlog post on itch.io that explains how the blips were designed — not a promotional post, but a behind-the-scenes post — appears in the Developer Logs feed and reaches the seller's followers. A post in a game development community that links to the pack with a description of what it contains is another source. A short demo video or audio preview embedded on the pack page gives the buyer a reason to click beyond the cover image.

The selling sound effects guide covers the broader marketplace landscape; itch.io is one channel among several, and the traffic strategy for each channel is different. On itch.io, the traffic strategy is community participation rather than paid promotion. A seller who is active in the game development community and has a pack that solves a specific problem — "I need UI blips that are not annoying" — will sell more than a seller who uploads a pack and waits for the algorithm.

The first sale is also more likely if the pack has a free demo. A free pack of five blips, with a clear link to the paid pack of sixty, lets the buyer test the quality before committing. The free pack is not a loss; it is the sample that makes the paid pack credible. A seller who has a free blip pack and a paid blip pack is in a better position than a seller who only has a paid pack, because the free pack brings traffic to the page and the paid pack converts the buyers who like what they hear.

The pack that sells is the pack that is easy to buy. That means a clear title, a cover image that reads at thumbnail size, tags that put it on the right shelf, a description that answers the buyer's questions in the first three lines, a license that removes uncertainty, and a ZIP that opens to a organized, documented set. None of these elements is expensive to produce. Each one is a decision, and the packs that sell are the ones where the seller made all of them.

Generate the Blips for Your First Pack

Open the SfxMaker blip generator and create a consistent set of 20 to 60 blips using the frequency and envelope ranges from the blip guides. Export them as WAV files, then package them with a README, a license, and a CSV manifest before uploading to itch.io. A documented pack with a clear license is worth more per sale than an undocumented one, even if the sounds are identical.

Open Blip Sound Generator →
Advertisement