How to Share a VO Pads Project and What Browser Limits Apply

Updated

VO Pads shares a project by URL: once your pads, clips, and playback settings are in place, the whole project is distributed as a single link, and anyone who opens it plays the project exactly as you configured it — no download or install on their side. The main constraint to plan around is iOS/iPadOS, where only one video can play at a time. VO Pads is a web app, so it runs in any browser that supports HTML5, with Chrome recommended for the best experience.

Sharing a VO Pads project

The share model is link-based rather than file-based. According to the site, you "share your entire project with a single URL" and "anyone with the link can open and play your project exactly as you've set it up."

What that means in practice:

  • You send a link, not a file. There is no export step described, and no download or install is required for the recipient.
  • The recipient sees your setup, not a blank player. Pad assignments, clip choices, and playback settings travel with the project.
  • The link is the whole project. Because the project is the URL, treat the link the way you would treat an unlisted performance: whoever has it can open and play it.
  • It suits collaboration and live performance. The site lists both as the intended uses, since a collaborator or performer only needs to open the URL.

What to check before you send the link

  1. Confirm each pad plays what you expect. Trigger the pads yourself in the browser you plan to perform or share from.
  2. Check timing and audio settings. Start point, duration, playback speed, and volume are part of the project, so a clip that starts late or plays too loud will behave the same way for everyone who opens the link.
  3. Open the link in a second browser or window. This is the closest thing to a recipient's experience without needing their device.
  4. Tell iOS/iPadOS recipients what to expect. If your project relies on overlapping video, they will not hear or see it the way you designed it (see below).

Browser and platform limitations

Condition What happens
Any browser with HTML5 support VO Pads runs; no download or installation needed
Chrome Recommended for the best experience
iOS or iPadOS Only one video can be played at a time

The iOS/iPadOS restriction is the one that changes how you build a project. If your sequence depends on two or more videos sounding or showing simultaneously, an iPhone or iPad viewer will not get that result. Options:

  • Design for one video at a time if your audience is likely to be on iOS or iPadOS.
  • Keep layered or overlapping sections for desktop viewers and note the limitation when you share.
  • Test on the target device before a live performance rather than assuming the desktop behavior carries over.

What sources a shared project can contain

VO Pads currently supports YouTube videos and local mp4 files. To add one, you tap a pad to bring up a selector, then either add a file or paste a YouTube URL. This matters for sharing because the two source types behave differently for whoever opens your link:

  • YouTube clips are referenced by URL, so the recipient streams them from YouTube.
  • Local mp4 files are files you added from your own device. The site does not describe a file-hosting or upload step, so if a recipient's playback depends on those files, verify the shared link actually plays them before relying on it for a performance or a handoff.

Quick answers

Do recipients need to install anything? No. VO Pads runs entirely in the browser; they open the URL and play.

Which browser should they use? Any HTML5-capable browser works. Chrome is recommended.

Can two videos play at once? On desktop, pad-based triggering is the point of the tool. On iOS or iPadOS, only one video plays at a time.

Is there a download or export? Not according to the site — sharing is done with a single URL.