How Should an Indie Game Composer in Spain Combine Steam Credits, Bandcamp, and Audio Reels?

An indie game composer should create one portfolio entry per game or standalone soundtrack, state the exact music and audio role, and link to the strongest public proof such as the released game, soundtrack, or focused reel.

A Steam page proves the game shipped, Bandcamp or SoundCloud can make the music easy to hear, and a reel can show range. The portfolio should connect those pieces without duplicating one title or implying credit for sound design, implementation, or composition you did not perform.

What should each game-audio entry contain?

Each entry should contain the title, release state, your exact role, a short description of the audio contribution, and one reliable listening or project destination.

Distinguish composition, sound design, dialogue editing, implementation, mixing, and audio direction. For a team project, name only your contribution and let the linked credits or case page provide the wider context.

Use the tag for a useful format or role, and add a metric only when the number is public, relevant, and yours to cite. A good description is more valuable than an unsupported play count.

What is the fast way to build the game-audio portfolio with IndieShow?

The fast way is to add one IndieShow card per released game, soundtrack, reel, or active collaboration and sort the cards by current status.

Use a permitted game or album image, write your role in the description, and point the single card link to the destination that helps the intended client listen or verify the credit fastest.

Put released games and finished soundtracks in Shipped or Built, current collaborations in Building or Working on, unsuccessful pitches in Womp womp when useful, and old unavailable projects in Archived.

Build your IndieShow pageClaim your handle, organise the evidence in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.

Should a project link to Steam, Bandcamp, SoundCloud, or a reel?

Link to the released game when shipping credit matters most, and to a soundtrack or focused reel when listening is the main decision the visitor needs to make.

Do not create several cards for the same game merely to expose every platform. A separate soundtrack album can be its own entry when it is a standalone release with a distinct audience and destination.

Check that the chosen page works without an account and that the relevant track or credit is easy to find. Replace dead or region-limited destinations when a stable authorised alternative exists.

How do you present prototypes and unreleased pitches?

Label prototypes and pitches by their real state, publish audio only when the agreement permits it, and never present a pitch as a shipped credit.

A public jam game or self-initiated cue can demonstrate work if it is clearly described. Material written for an unreleased client project may need to stay private even if you composed it.

Move abandoned public experiments to Archived rather than mixing them with current commissions. Honest status helps a collaborator understand both experience and availability.

Related IndieShow reading: organising released games and prototypes · preparing a focused event link

How does IndieShow create one useful composer link?

IndieShow creates one useful link by arranging released titles, listenable work, active collaborations, and archived experiments as consistent project cards on a single personal page.

The page can also carry your profile bio and supported social links, while each project keeps one focused destination. Update the card when a game launches or a soundtrack becomes publicly available.

That IndieShow link can serve bios, applications, and outreach without forcing every listener to search separate stores and audio platforms for the context behind your work.