Audio
Use Audio to add a playable sound file, podcast clip, message, or audio asset to a page.
Content settings
| Setting | What it controls |
|---|---|
| Audio source | The uploaded or selected audio file. |
| Playback controls | Player controls exposed by the browser or element. |
| Metadata | Audio title or supporting information when available. |
Style settings
| Style area | What you can adjust |
|---|---|
| Size | Width, height, and responsive sizing. |
| Alignment | Left, center, right, or full-width placement. |
| Container | Background, border, radius, shadow, margin, and padding. |
Best practices
- Test playback on mobile and desktop.
- Do not rely on autoplay; browser policies can block it.
- Compress audio files before upload when possible.
FAQ
When should I use this page?
Use this page when you need a quick reference for this Atomicat feature and want to understand what it changes before editing or publishing. It is especially useful while reviewing a page, funnel, quiz, lead flow, product setup, video configuration, or account setting. For Audio, keep a short checklist of the fields you changed and test the result in the same browser session.
Do I need to configure this before publishing?
Configure it before publishing whenever the feature affects visitor behavior, tracking, SEO, forms, embeds, checkout, or access. If the feature only changes internal organization, review it before launch so your team can manage the campaign consistently. For Audio, keep a short checklist of the fields you changed and test the result in the same browser session.
Can this affect live pages?
Yes, some settings can affect live pages after saving or publishing. Always preview the page, test the main action, and confirm desktop and mobile behavior before sending paid traffic or sharing the URL. For Audio, keep a short checklist of the fields you changed and test the result in the same browser session.
What should I check if something looks wrong?
Check the page status, project access, saved revisions, browser cache, connected domain, and any related integrations. If the feature depends on a plan, permission, or enabled module, confirm that your workspace has access. For Audio, keep a short checklist of the fields you changed and test the result in the same browser session.