Protected client preview
Create a protected client preview
Create an audibly marked preview for clients without sharing the final audio file.
Your result
An MP3 preview with an audible watermark
Access and price
Included with eligible Audiocrowd subscriptions
Premium workflow: included with eligible Audiocrowd subscriptions. A separate one-off purchase is not currently configured.
Intended for eligible Audiocrowd subscriptions.
No one-off purchase price is configured.
Tool access and any separate music license are separate concepts.
Next step
Do you need more support after the preview?
The protected client preview is designed for controlled sharing. Managed support can help with advanced protection requirements or an individual assessment.
-
Contact managed support
For advanced protection and approval requirements.
At a glance
- Access
- Included with eligible Audiocrowd subscriptions
- Input
- One audio file · .aac, .aiff, .flac, .m4a, .mp3, .oga, .ogg, .opus, .wav
- Output
- An MP3 preview with an audible watermark
- Handling
- Private and stored temporarily
- Account
- An Audiocrowd account with an eligible subscription is required.
In three steps
How the workflow works
- Securely upload the audio file and have it checked
- Choose the watermark length, position, and level
- Download the individualized MP3 preview
Available now · Premium tool · Included with eligible Audiocrowd subscriptions
Access and scope at a glance
This client preview is a dedicated Audiocrowd Tools workflow. Tool usage and music-license downloads remain separate areas.
Intended for eligible Audiocrowd subscriptions.
No one-off purchase price is configured.
Workflow
How your client preview is created
The workflow focuses on controlled preview sharing rather than final delivery or a full DAW process.
- Securely upload the unreleased audio file and have it technically checked
- Generate a standard preview with an audible watermark
- Remove metadata when needed and generate an individualized preview
- Share the finished MP3 preview in a time-limited and controlled way
Available now: audible-marked client preview
The current version creates a full or trimmed MP3 preview, removes file metadata, and adds an audible Audiocrowd watermark. Choose the preview length, position, and level; an optional recipient reference can help with internal attribution.
Audio files are stored privately and only temporarily. Input and output are automatically deleted after the configured retention period; signed download links expire separately.
View all Audio ToolsAudible mark and additional protection layers
Audible watermark
The mark is intentionally audible. It signals that the file is a preview and supports attribution of an individualized export.
Robust or forensic
Robust or forensic watermarking can serve as an additional protection and identification layer. Claims about resilience apply only to transformations covered by documented tests.
What kind of client previews is this workflow for?
- Unreleased tracks for clients, labels, or agencies
- Individualized approvals with traceable recipient attribution
- MP3 previews where unnecessary metadata should not be shared
- Temporary sharing with a clear separation between preview and final delivery
Frequently asked questions about protected client previews
What is a protected client preview with an audible mark for?
An audible mark shows the recipient that the file is a client preview and supports attribution. It discourages uncontrolled sharing but is not a guarantee against every form of editing or removal.
What is an additional robust or forensic protection layer?
An audible watermark is directly perceptible and intended for client previews. Robust or forensic watermarking is an optional advanced layer for identification after common processing steps and is evaluated separately.
Which files can I use?
The Tools area checks audio files server-side. Supported formats follow the current Audio Tools configuration: AAC, AIFF, FLAC, M4A, MP3, OGA, OGG, OPUS, WAV. File size, duration, and technical audio data are checked before processing.
Are customer details stored in the audio file?
A preview should be associated server-side through its job identity. The audio file should contain only technical output data that is needed, not unnecessary personal recipient information.
Share the right client preview
Learn about the flow for a time-limited, personalized preview and register your interest.
