How Podcasters Can Collect Guest Audio and Discuss Episode Files

For independent podcasters, the gap between a guest’s raw recording and a polished episode is often filled with file-size errors, forgotten attachments, and version confusion. A practical two-step workflow using ShareIt.onl solves this: collect high-quality local recordings via a Request Files link, then use a private Group Chat to coordinate revisions and deliver the final mix. This method keeps guest audio separate from production chatter and avoids the security pitfalls of using chat apps for confidential data.

Why Local Recordings Matter

Remote recording platforms can tie audio to a server you cannot control. Asking a guest to record locally on their own device—using a free tool like Audacity, QuickTime Player, or a smartphone voice-memo app—gives you an isolated track. The challenge is getting that large WAV or AIFF file from the guest to your editing timeline without email bounce-backs.

Step 1: Collect Guest Audio with a Request Files Link

ShareIt.onl’s Request Files feature is built for exactly this handoff. You sign in free with a Google account, create an inbox link, and send it to your guest. The guest clicks the link in any browser, uploads their file (up to 100 files or 3 GB per delivery), and you receive a notification. No app, no account, no sign-up for the guest.

Setting Up the Request

1. Go to ShareIt Online Request Files and sign in with Google.
2. Choose a link duration: 7 days or 30 days. This is how long the inbox link remains active for new uploads.
3. Copy the link and send it to your guest via email or a direct message. Include a brief note: “Please upload your local recording here. WAV or AIFF preferred. Name the file as FirstName_EpisodeNumber.wav.”

What the Guest Sees

The guest opens the link, selects their file, and uploads it without creating an account. You receive the file in your ShareIt.onl inbox, where it is stored for 7 days. Each owner download extends that file's availability by 24 hours, so download important recordings promptly and keep your own backup.

File-Naming and Consent

Before sending the link, establish a naming convention. A file named “recording.m4a” is a liability; “Smith_Ep42_Take1.wav” is a production asset. Include a line in your pre-interview email: “By uploading, you confirm consent to use this recording for the episode.” The Request Files link itself does not capture consent, so keep that email thread separate.

Step 2: Coordinate Revisions and Deliver the Mix in a Private Group Chat

Once you have the raw audio, the editing begins. You will likely need to send the guest a rough cut for fact-checking, share a revised mix after their notes, and finally deliver the mastered episode. This is where ShareIt.onl’s Group Chat becomes useful—but only if you understand its boundaries.

Setting Up the Group

Group Chat is invitation-only and requires every member to sign in with a Google-connected account. Create a chat for the episode, invite your guest and any co-producers, and keep the conversation to production logistics: “Rough cut is ready,” “Check the intro level at 0:45,” “Final mix attached.”

Attaching Files the Right Way

You can share an active ShareIt.onl link from My Files or add a new attachment copy in the chat. Message text, filenames, and new chat attachment copies are encrypted and decrypted in members' browsers with AES-256-GCM. Original items in My Files remain separate and keep their normal ShareIt controls, so do not assume the chat's encryption description changes how those originals are handled.

To share a mix from My Files:

1. Upload the finished mix to My Files (or reuse a file already there).
2. Generate a share link with an expiry that matches your production timeline.
3. Paste that link into the Group Chat. Members click it and download the file in their browser.

Why Chat Is Not for Confidential Guest Data

Group Chat's encryption applies to its message text, filenames, and new attachment copies. A reusable My Files link follows its own normal ShareIt controls. More importantly, a production chat is not the right place for signed release forms, payment details, or home addresses. Keep that information in a dedicated, access-controlled system and use Group Chat for file delivery and time-sensitive production notes.

Troubleshooting and Common Mistakes

The Guest’s File Is Too Large

ShareIt.onl’s Request Files accepts up to 3 GB per delivery. Check the exported file size before sending the request. If it exceeds 3 GB, ask the guest to export as lossless FLAC when appropriate or split the recording into clearly numbered parts.

The Link Expired Before You Downloaded

Request Files inbox links accept uploads for 7 or 30 days, while received files have their own 7-day retention period. Each owner download extends a received file by 24 hours. Set reminders around both deadlines and save a local backup as soon as the recording arrives.

The Guest Uploaded the Wrong File

Ask the guest to upload the corrected take with an unmistakable version name, such as Smith_Ep42_Take2.wav. Keep only the approved version in your production folder so the editor cannot grab the wrong take.

Group Chat Members Cannot See the Attached Link

Ensure the file in My Files has a share link that is still active. If the link expired, generate a new one and paste it into the chat. Group Chat does not automatically refresh dead links.

Practical Advice for a Smooth Workflow

Send the Request Files link immediately after scheduling the interview, not the day before. Include a one-sentence recording guide: “Record in a quiet room, use a wired microphone if possible, and export as WAV or FLAC.” After you finish the edit, upload the rough mix to My Files with a password, then share the link in Group Chat. When the guest approves, deliver the final mix the same way. After publication, remove links you no longer want active and retain your production archive in the storage system you normally use.

This separation of collection and collaboration respects both audio quality and data boundaries. Your guest records once, uploads once, and never has to wonder which version of the file you are working from.