Send Podcast Audio to a Client Without a New Account

A finished episode is ready. The client needs the WAV master, the MP3 for publishing and a short note identifying the approved version. They do not necessarily need access to your editing workspace—or another account to collect three files.

Disclosure: I work with SEAL. This practical guide was prepared with AI assistance. The example below is hypothetical, not a customer case study.

Start with the delivery package

Export the agreed deliverables rather than sending an entire working session by default. Keep filenames unambiguous: Episode_12_final_v3.wav is more useful than final_final.wav. Include a short delivery note listing the files, version and any agreed next step.

Check that the package does not accidentally include unreleased outtakes, private production notes or third-party assets you are not allowed to redistribute. Keep your source session and a separate backup. A delivery link is not your archive.

For example, a 400 MB package containing a finished WAV, an MP3 and a transcript could fit a temporary-transfer workflow. Check the actual total before choosing a service; a long multitrack session or a large set of stems may need a different plan.

Agree on the deadline before uploading

Ask when the client will collect the files. Choose a link lifetime that covers that window, and include the expiry in the delivery message. If they cannot download within the available period, use a longer-lived option rather than hoping the link will still work.

SEAL's current free tier allows up to 1 GB per seal for up to seven days. It is a temporary handoff, not unlimited storage. Larger or longer-lived seals have paid options; check the current pricing instead of assuming the free limits will cover every job.

Send the download link, not the management link

On the SEAL homepage, choose Tap to send and add the agreed files. SEAL encrypts file contents in your browser before upload. Neither the sender nor the recipient needs a SEAL account for the browser handoff.

The result provides a recipient link and a private management link. Send the link labelled “Send this” to your client. Keep the link labelled “Keep this” for yourself: it controls the seal and is not a second client-download link.

If you choose a password, share it through a separate agreed channel. Use a single-use rule only when it matches the recipient's workflow; an unnecessarily restrictive link can make checking and collecting a package harder. Never describe access rules as a substitute for checking who you sent the link to.

Ask for a receipt—not a platform signup

A useful delivery message names the episode, lists the deliverables, states the collection deadline and asks the client to confirm that the files downloaded correctly. They can save their own copy and inspect the audio in their usual player or editor.

SEAL is not a podcast host, an audio player, a transcription service or a revision-approval workspace. If the client needs timestamped feedback, collaborative editing or a permanent episode library, use a tool designed for that job.

Revocation stops future access; it does not erase copies already downloaded. Only send material the recipient is authorised to receive.

Try this workflow for your next finished episode: Tap to send on SEAL

Current limits: https://seal.net/pricing

Browser instructions: https://seal.net/docs/web

Related reading: Deliver original photos and videos to a client.

Having trouble collecting a delivery? Read Your Client Cannot Download a File: What to Check.