One pass. Title, thumbnail, playlist, schedule.
Browser to YouTube
Nothing
Thumbnail and playlist
Runsheet never holds your video
The server opens a resumable upload session with YouTube and hands the URL back to your browser. Your browser sends the bytes directly to Google. Runsheet sees the metadata and the progress, never the file.
That is a deliberate design rather than a limitation we are dressing up. There is no copy of your unreleased work on anyone’s server, there is no storage bill that eventually has to appear on your invoice, and a platform breach at our end cannot leak a video.
Two permissions, asked for on purpose
Google separates uploading a video from writing to a playlist. Plenty of tools request the upload scope only, which is why their videos land unfiled and you tidy them up in Studio afterwards. Runsheet asks for both, so a video is in the right playlist the moment it exists.
Best effort after the upload, and it says so
Once a video is on YouTube it cannot be un-uploaded. So everything after that point is best effort by design: if the thumbnail is rejected or the playlist write fails, Runsheet warns and leaves the video alone rather than trying to unwind something that cannot be unwound. You get a specific message and a retry, not a red banner that says something went wrong.
What this feature will not do, stated where you can read it before paying.
- Playlist filing and thumbnails are best effort. If one fails the upload is still done, and you are told.
- Thumbnail upload requires a verified YouTube account, which is Google's rule, not ours.
- A video already published cannot be unpublished from Runsheet.