How Should an Audio Plug-in Developer in Spain Show VST3, Audio Unit, Demos, and Store Listings?

An audio plug-in developer should present each distinct plug-in as one project, state their engineering and product contribution, list only currently supported formats, and link the best maintained product, documentation, or demo page.

VST3 and Audio Unit builds are formats of one product, while an audio demo proves sound and documentation proves setup. The portfolio should connect those surfaces and describe whether you owned DSP, interface, preset design, packaging, or only one part.

Which audio plug-ins belong in the portfolio?

Include released products, maintained free tools, substantial approved client work, and archived plug-ins that still demonstrate relevant engineering without pretending they remain supported.

Make one card per distinct effect, instrument, or developer tool, not per operating system or plug-in format. For collaborations, name your part: DSP, native code, UI, framework integration, testing, installer, or product work.

Use Shipped or Built for usable releases, Building for active development, and Archived for discontinued binaries. A prototype with no safe build can still be described honestly without a download link.

Released plug-in: maintained product or documentation page.
Sound proof: stable audio or video demo.
Public framework/tool: repository with setup guidance.
Private client DSP: approved case description only.

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

The fast way is to add one IndieShow project per plug-in, assign its present status, and use the card destination as the maintained front door.

Put the product category or supported format in a short tag and use the description for what it does and what you built. Add a logo and an optional metric only when you own or can publish the number.

Order current products before experiments and use the dashboard preview to check that the page makes sense without hearing every demo first.

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

Should VST3, Audio Unit, the store, and the demo be separate cards?

No; formats, checkout, documentation, and demos should stay under one plug-in project unless one component is an independent developer product.

Choose the product or documentation page when it routes visitors to compatible installers and demos. Choose a public repository when the engineering tool itself is the work being evaluated.

Do not send visitors to direct binary files, expired checkout pages, or unsupported installers. State compatibility only as it exists today.

How do you show private DSP or client audio work?

Describe the signal-processing problem, your exact role, and approved proof without publishing source code, unreleased audio, client builds, or confidential product plans.

A before-and-after demo can be used only when you own the material and have permission. Otherwise a precise anonymised summary is safer than a leaked binary or private repository.

The related IndieShow guides cover game-audio credit and cross-marketplace plug-ins, both useful for attribution and format boundaries.

How does IndieShow keep an audio developer portfolio accurate?

IndieShow keeps one public product index accurate while stores, documentation, repositories, and media hosts supply the specialised audio evidence.

Move discontinued products to Archived, update supported destinations, and remove demos or installers that no longer represent the release. Keep current work first.

IndieShow closes the portfolio with one stable personal link and a clear explanation of what you built before anyone opens a store or presses play.