The store page is open on a laptop, next to an engine project, and the buyer is three tabs deep. The preview starts before the page finishes painting. They listen for eight or ten seconds, scroll the file list, look for a sample rate, look for a licence, and close the tab. Twenty seconds is a generous estimate for the whole sequence.
Almost nothing in that sequence is a judgement about whether the heal cue is beautiful. It is a check against a short list of questions a stranger asks in order, and most of the pack design work is arranging things so those questions answer themselves.
The Four Checks a Buyer Runs Before Listening Closely
The first check is the preview, and it plays on whatever the laptop has. Most laptop speakers roll off hard below roughly 200 Hz and thin out above 8 kHz, which leaves the 300 Hz to 3 kHz band carrying nearly all of the message. A heal cue built around a warm 120 Hz body can feel good on headphones and almost vanish in the audition. Play the preview on a phone speaker at half volume before publishing it.
The second check is the file list. The buyer is not reading every name so much as counting. Three variants and a folder of twenty read as different products from the same seller, and the list also answers whether the pack covers sizes at all. A scroll that reads small, large, party, over time, denied does that job in one glance.
The third check is format and sample rate. Anyone who has shipped a build before knows what their engine wants: 48 kHz mono WAV for spatialised cues, 44.1 kHz if the project has not moved, OGG when the build size is tight. If the buyer has to open the listing in a text editor and search for the number 48, the pack that states it in the third line wins. The practical mechanics of listing a pack this way are covered in creating and selling sound packs .
The fourth check is the licence. Commercial use in a game, yes; redistribution of the raw files, usually no; credit, sometimes. A buyer who has been burned by an unclear licence will send a message, and that message turns a thirty-second sale into a three-day thread.
Route the Demo as an Escalation, Not a Sampler
A preview that plays five similar heal chimes in a row tells the buyer very little. The audio is half the information; the order carries the other half, because each entry answers the question the previous one raised. Does the family scale? Does it handle a group? Does it handle regeneration? Does it handle a heal that does not apply?
Small heal first, under a second, so the base palette lands. Large heal second, longer and lower, which shows whether the same family stretches without turning into a different product. Party heal third, because anyone shipping co-op wants to know the pack thought about overlap. Heal over time fourth, a few seconds of repeating ticks, because that is the entry most packs leave out and the one that most often turns into a refund request. Denied heal last: the dull buzz when health is already full. That one small entry makes a pack feel like it came from someone who plays the game. It is also the part of the offer a generated effect rarely covers, which is the argument laid out in packs versus generated effects .
Leave 600 to 900 ms of silence between entries. Trim the head of each file so the first sample sits no more than 20 ms from the attack; a 200 ms fade-in at the top of a preview reads as hesitation. Leave the music out entirely. A bed masks the 300 Hz to 2 kHz band where the heal identity lives, and a buyer listening against music cannot judge the cue they are about to import. Keep the preview entries at a consistent loudness, around -16 LUFS integrated, so the small heal does not sound weak next to the large one.
Ship the escalation as one file, not five players. A page with five separate play buttons invites the buyer to click the prettiest one first, which puts the running order back in their hands and usually skips the regeneration ticks. One stereo render, 60 to 90 seconds, with the five entries in order and short gaps, keeps the story intact in a browser tab, in a store embed, and in a zip folder someone opens on a commute.
Names That Sort and Read at a Glance
The file browser is the second interface the buyer meets. In many engines folder nesting is flattened on import, which leaves the name as the only structure that survives. That makes naming an ordering decision as much as a labelling one.
Use one prefix for the whole family, lowercase, with underscores. Pad the index to two digits so the column sorts 01 through 05 instead of 1, 10, 2. Put the descriptive word last, so a scan down the list reads as a column of sizes. No spaces, no capitals, no version numbers in the name. Suffixes like final, new and v2 tell the buyer they are looking at a working folder rather than a finished product.
The Filename Pattern
- heal_01_small.wav
- heal_02_large.wav
- heal_03_party.wav
- heal_04_regen_tick.wav
- heal_05_denied.wav
When the pack ships in more than one format, let the extension carry that and mirror the names exactly across the format folders. A buyer who imports the OGG set by mistake should be able to drop in the WAV set without remapping anything.
Folders That Mirror the Demo Order
The pack root should read the way the preview played. One Audio folder, flat, holding the prefixed files in demo order, a Demo folder with the preview render, and a README plus a licence file at the root. Two levels is enough. Deeper nesting looks tidy on the seller machine and tends to disappear on import.
Flat files inside Audio have a practical payoff: the buyer can drag the folder into the engine, sort by name, and get back the order they just heard. If the folder order and the preview disagree, the buyer has to rebuild the sequence in their head, and that is usually the moment the tab closes.
The README Carries the Contract
The README is where the buyer checks the details they did not want to ask about. Three things belong in it, and nothing else has to be there: the licence in plain sentences, a format table, and the loudness target. Not a marketing paragraph, not a feature list, not a note about the artist.
| Property | Stated value |
|---|---|
| Format | WAV, 48 kHz, 24-bit, mono; OGG Vorbis 48 kHz copy |
| Loudness | Files at -18 LUFS integrated, true peak -3 dBTP; preview rendered at -16 LUFS |
| Tail | 200 to 400 ms of silence after the last audible sample |
| Naming | heal_ plus two-digit index plus description |
The licence paragraph should be short enough to read without scrolling: what the buyer may do with the files in a commercial build, whether the raw files may be redistributed, and whether credit is required. If the pack has a free tier and a paid tier, the same paragraph has to say what changes between them; the trade-offs around that split are covered in free versus paid effects .
The Listing Copy Should Promise One Specific Thing
Premium heal sounds for your game is not a promise. It cannot be wrong, so it cannot be checked, so it does not help. A sentence the buyer can verify against the preview does help: five cues covering small, large, party, regeneration and denied heals, 48 kHz mono WAV, named for direct import, licence printed in the README.
Put that sentence first. Put format and licence on the second line. Move the adjectives to the end, or cut them. A buyer scanning for a pack that fits their pipeline is looking for the words 48 kHz and WAV, and a paragraph of atmosphere between them and the download button is a cost, not a selling point.
One last check before publishing: open the pack folder on a machine that has none of your tools installed, sort by name, and play the preview from the top. If the sequence still explains itself there, the pack is doing what the listing promises.