How to Use Bandcamp Download Codes for an Album

What does a Bandcamp download code give the recipient?

Bandcamp calls these track/album codes. They give the recipient a digital copy of the selected release, with a download and streaming through the Bandcamp app. They can be useful for a reviewer, a fan receiving a merch insert, or someone you want to give a copy directly.

The official track/album code tutorial covers generation and redemption. Decide which release the recipient should receive before you make a batch. An album code and a track code do different jobs.

Keep the offer clear. If a card comes with a cassette, say which digital release it provides. If you are sending a press copy, identify the album and release date in the message. Receiving a code should not leave someone guessing what they have been sent.

The Bandcamp pricing guide owns the discount-code setup. Keep your complimentary-copy record separate from a price-promotion report.

How do you generate a named batch?

Open the Track/album codes section of your Bandcamp Tools page. Choose the downloadable release, give the batch a useful name, and enter the quantity. Bandcamp currently documents generation in multiples of 100. Check your account's available codes and any purchase requirement before continuing.

The batch name is for your own organization. Bandcamp says fans do not see it. Use something you can recognize later, such as the release name plus Press Copies or Cassette Inserts. Generating a new batch should answer a specific distribution need.

1. Confirm the exact track or album selected in Tools.
2. Generate the named batch and open its export link.
3. Save the CSV in your release working folder and open it in a spreadsheet.
4. Reserve a small test allocation before preparing recipient messages or printed cards.

Bandcamp also provides a print link for its card layout. If you use a print shop or design your own cards, confirm how unique codes will be merged into the artwork. Review a proof before ordering the full run.

How should you allocate and send the codes?

Give every allocated code one intended destination in your own record. That might be a named reviewer, a numbered merch insert, or a particular show batch. This is an operating choice that helps you avoid accidentally sending the same code twice.

Keep fields for release, batch, code, destination, allocation status, sent date, and redemption status. A code can be reserved before it is sent. A sent code can remain unredeemed. Preserve those distinctions when more than one person is helping with the campaign.

Include your account's redemption page, which Bandcamp documents in the form youraccount.bandcamp.com/yum. Check your actual address before printing or sending it. You can send the code in an individual message or place it on a card beside the redemption instructions.

For a larger email send, verify that your mailing tool inserts a different allocated code into each intended message. Review several test messages for missing values and repeated codes. Use a list you are entitled to message, and keep the full code export out of publicly shared campaign documents.

Test the handoff before you send the batch

Test the format you intend to distribute. A successful copy-and-paste from your own spreadsheet does not prove a printed code is legible or an email template contains the right value. Read the message as someone who has never seen your Tools page.

Use your reserved test allocation to check the selected release. If the result is wrong, stop the send and correct the batch or delivery material. Do not keep distributing cards while hoping the link is close enough.

The Bandcamp pre-order guide covers the public offer and launch. Keep that public release promise beside your early-copy plan.

A small batch with a clear allocation record

The release coordinator marks the two test allocations as used for testing after checking the handoff. Each reviewer allocation gets an agreed destination and sent date. Nobody sends codes from the unassigned group until the coordinator records the new allocation.

If a second teammate prepares cassette inserts, they receive a newly allocated group. They do not pick codes from the same untouched export independently. The point is to make duplicate distribution visible before a recipient reports trouble.

Plan the public release messages alongside the complimentary-copy handoff →

How do you check which codes were redeemed?

Bandcamp's redemption instructions point to the blue number in the redeemed column of the Tools page. Use that redeemed-code list to reconcile your own allocations.

Match by the code itself. Keep the exported file dated so your team knows when the comparison was made. Record mismatches for review rather than overwriting the original send record.

Report generated, allocated, sent, and redeemed quantities separately. A code that has not been redeemed could still be sitting in a recipient's inbox or on an unclaimed card. Redemption alone does not establish how much someone listened, whether they liked the album, or whether a reviewer will cover it.

For the wider storefront and campaign, return to the Bandcamp guide for artists. Your code record is one part of that release operation.

Official code instructions