What's New in Tubeup 2.0?

When we shipped Tubeup 1.0, the goal was narrow and concrete: make the part after the edit, all the typing and clicking and uploading, take minutes instead of an evening. It worked. You enlisted a folder, generated metadata, clicked upload, and a batch that used to eat a night was done before dinner.

But 1.0 was a very fast pair of hands, and hands still need someone attached. Every session needed you sitting in front of it. The upload got faster; the presence it required didn't change.

Tubeup 2.0 removes the sitting. One line captures it: Tubeup 1.0 uploaded your videos. Tubeup 2.0 runs your channel.

Version 2.0.0 shipped on 20 September 2026. This is the full story of what changed, what was added, what was fixed, what was hardened, and why each piece matters if you publish on YouTube for a living.

The short version

If you read nothing else, here's the release in one table:

	Tubeup 1.0	Tubeup 2.0
Publishing	You click upload	Flows upload on a schedule, while you're away
Control	Menus and forms	Menus, forms, or plain English
AI providers	Gemini	9 providers, including local models; the default has no per-word cost
Channels (API engine)	One; the second replaced the first	As many as you own, on one Google project
Descriptions	Global defaults, retyped per video	Named content profiles, applied in bulk
Channel per video	The default channel	Chosen on the row
Backup	Settings	The whole install: videos, profiles, flows, chats
Trying it	Buy first	3-day free trial, no card
Closing the window	Everything stops	Automation can keep running in the tray
Startup	1.44 s, 154 MB	0.56 s, 53 MB
Double-publish risk	Three known paths	Closed
Local backend	Reachable by any web page	Locked to Tubeup's own window

Now the long version.

Added: five features that change how you publish

1. Automation flows: the app works while you don't

A flow runs Tubeup's own pipeline on a loop — watch a folder, write the metadata, upload, promote — and each step does exactly what its button on the Dashboard does. We designed it that way on purpose. There's no second, hidden automation engine behaving differently from the app you already know. A flow presses the same buttons you would, on a schedule.

Each flow has its own schedule, a daily cap so it can't run through your quota, an activity log, and a backlog view of queued work. Before you trust it with a real run, press Simulate and watch the whole thing: the exact videos, metadata and destinations, before a single video moves.

The detail I'm proudest of is small: a pause is always explained. Not "flow stopped", but quota exceeded, this channel is no longer connected, or three failures in a row. Anyone who has used automation software knows the feeling of finding a job that quietly died days ago. That can't happen here without Tubeup telling you why.

By default, flows run while Tubeup is open. If you want them to keep going after you close the window, turn on Keep running in the tray. It's off by default, because an app that refuses to close when you didn't ask it to is its own kind of bug.

2. Chat: run Tubeup by typing

2.0 adds a chat dock that opens over any page. Ask it about your library and it answers. Tell it to do something and it proposes the change. It's not a help bot; it has 14 real actions: set a schedule, set visibility, set a playlist, edit fields, generate metadata, generate social copy, upload, cancel an upload, delete videos, apply a content profile, edit a content profile, check automation status, pause automation, and enlist new videos.

"Set every video in this batch to Unlisted and schedule them 6pm daily starting Monday" becomes one sentence and a confirmation instead of forty clicks.

That confirmation is the trust story. Every action is shown as a diff and waits for you. The model picks an action from a fixed registry and never writes to your library directly. Nothing runs until you say run.

3. Nine AI providers, and the default has no per-word bill

1.0 used Google Gemini. 2.0 supports Revoye, Google Gemini, Anthropic, OpenAI, DeepSeek, Qwen (DashScope), Perplexity, OpenRouter, any OpenAI-compatible server, and local models through Ollama or LM Studio. Every provider's model is editable, because vendors retire models on their own schedule, and each one comes pre-filled with the model it would otherwise use.

Revoye is the new default and appears first in every picker. It runs prompts through the AI accounts you're already signed into, so there's nothing per-word to pay. Metadata for a 200-video batch no longer comes with an API bill that grows with your output. Revoye's dashboard now lives at revoye.com and its API at api.revoye.com. If you'd rather keep everything on your own machine, point Tubeup at a local model and nothing leaves it.

Existing installs keep whichever provider they were already using. Nothing is switched under you.

4. Every channel you own, on one Google project

The API engine now connects as many channels as you like from a single Google Cloud project, with one client ID and secret. Press Authorize once per channel and pick that channel on Google's consent screen. In 1.0, connecting a second channel replaced the first, which was the thing agencies and multi-channel owners were blocked on. Optional per-channel credentials let you put one channel on its own Cloud project, and so its own daily quota.

The supporting pieces make it usable: one channel list across both engines, showing whether each channel is ready for Browser uploads, API uploads, or both; a channel filter in Analytics; per-video channel selection right on the video row, so a mixed batch goes to the right places in one pass; and a confirmation before removing a channel, which used to take a single click.

5. Content profiles: write your description once

A content profile is a named, reusable set of the blocks that make up a description: brand links, sponsor links, suggested links, timestamps, resource links, social links, hashtags and SEO tags, plus its own label visibility. Assign one to a channel, apply it to a batch, let a flow apply it automatically, or have the chat apply or edit it.

This is the biggest cut to repetitive typing in the app. Run different identities, like a sponsor set on one channel, an affiliate set on another, and a clean set on a third, and switch the whole description body by picking a name.

If you're upgrading: your 1.0 defaults are migrated into a permanent Global Default profile on first launch, so an upgraded install publishes byte-identical descriptions on day one. Nothing you wrote is lost or changed.

Added: the supporting cast

Each of these would have been a headline in a smaller release.

• Backup and restore the whole install. Every video row, setting, profile, flow and chat thread goes into one file, restored either over what's there or in place of it. 1.0 backed up settings; 2.0 backs up your work.
• Schedule from the video row. The schedule picker opens where the video is, and refuses a time in the past.
• Videos per request. Decide how many videos each AI request carries, to fit your provider's limits.
• A new identity. A new Tubeup logo and app icon, across the installers, window and tray. It's the first thing existing users will notice, and it's on this site too.
• A 3-day free trial with no card, so nobody has to buy first to find out whether flows fit their channel.

Changed: clearer names, a better app

Both upload engines were renamed. "Easy Unlimited Uploads" is now Browser, and "Reliable Uploads & Analytics" is now API. Nothing about how either works has changed; settings and flows migrate on first launch. The old names described a benefit. The new ones describe the mechanism — a real browser with your own YouTube Studio session, or Google's official API — which is the one thing that decides which engine you want. The Browser engine is still the one built to get past the official API's six-uploads-a-day limit; the API engine still lives within Google's quota.

Published is now Uploaded. It's a read-only preview of exactly what each video was uploaded with, so you can stop opening YouTube Studio to check what actually went out. Old links still resolve.

Settings were rebuilt, with tabbed sections, a search box that jumps to and highlights the exact row, Help moved in as its own tab, per-channel credentials, on-screen quota usage, and an unsaved-changes guard on the way out. Type "quota" and land on it.

Every view got a UI and UX pass: tighter 48px table rows that fit more videos on screen, unified scrollbars, standardized typography, clearer headers and alignment across Dashboard, Uploaded, Analytics and Social Share, more visible error messages, a column menu, and accessibility improvements throughout.

And the refinements power users notice:

• Click a video ID to copy it.
• The description preview shows the About text that will actually publish, not an approximation.
• Tubeup tells you when the server refuses a watch folder, instead of failing quietly.
• Escape closes one thing at a time.
• Dialogs keep focus, and a crash in one page can no longer blank the whole window.
• Removing the default channel picks a new one, and renaming a channel keeps its flows working.

Fixed: the things that could cost you a video

For anyone who has been burned by an upload tool, this section matters more than any feature list, so I'll frame it as what can no longer go wrong.

A video can no longer be published twice. There were three ways it could happen in 1.0: a retry after YouTube already had the file, a cancel that arrived after the save was confirmed, and a crash between the upload and the row being written. All three are closed.

The rest:

• Resumable API uploads. A large upload survives a dropped connection and continues from what the server actually holds, instead of restarting a multi-gigabyte file.
• Scheduling is all-or-nothing. If the date or time can't be set, the upload stops and says so, rather than publishing at YouTube's default time. Your 6am video never goes live at noon.
• No phantom records. A video is never recorded as uploaded on a transfer that didn't finish.
• Cancel means cancel. Cancelling an automation run stops it, and no longer counts as a failure against the flow.
• Fair scheduling. A paused flow no longer starves every other flow.
• Unsaved work stays put. A background refresh can't wipe the flow you're editing or the text you're typing.
• Failed saves are reported. No more values sitting on screen that were never actually stored.
• Bulk actions only touch rows you can see. A selection no longer survives a search that hides it, which could have deleted videos that weren't on screen.
• Restore is robust. A merge restore no longer fails when run history has moved on since the backup.
• Caps behave. An API upload step can be left uncapped, and a daily cap of 0 no longer becomes 6 on save.

Security: found it, fixed it, telling you

During the 2.0 hardening pass we found a real weakness, closed it before release, and want to say plainly what it was.

Tubeup's local backend is no longer reachable by web pages. The backend listens on your own machine, which any website open in your browser could also reach. Before this release, that was enough to read your settings (including decrypted AI keys), rename files, start uploads, or restore over your library. Now every launch mints a secret that the backend requires and that only Tubeup's own window is given, and requests aimed at a different hostname are refused outright.

Also hardened:

• A restored backup can't switch automation on, enable a flow that fails validation, or point your library at a folder that isn't there. A backup file is data, not a command.
• An unreadable stored key reads as empty, rather than being sent to a provider as though it were the key.
• The window is held to its own pages, and a stray background failure is logged instead of taking the backend down with it.

The standing promise hasn't changed. Your library, your keys and your sessions stay on your machine. Tubeup is a desktop app with a local database, and there is no Tubeup cloud holding your content.

Performance: the numbers

Measured on the packaged app:

Metric	1.0	2.0
Backend ready	1.44 s	0.56 s (~2.6× faster)
First screen	2.0 s	1.4 s
Backend memory	154 MB	53 MB (~100 MB lighter)

The main reason: the Google API and browser-automation libraries now load the first time they're needed, not at every launch.

At scale, with 5,000 videos in the library, the list answers in about 100 ms, pages open in under a second, and typing costs about 3 ms per keystroke. The database runs in WAL mode, enlisting thousands of files writes in batches, and polling does honest work: no stacked requests, and nothing polling behind a hidden window. That matters more in 2.0 than it did in 1.0, because an app you leave running all day has to be light.

Platform: installable on every modern Mac

macOS builds are always signed now, with a Developer ID certificate when configured and ad-hoc otherwise. Apple Silicon refuses unsigned builds outright, so this is what makes Tubeup installable on modern Macs at all. And a build check runs on every push to a release branch, building both installers and launching the packaged macOS app to prove it starts, before a release can ship.

If you're on Tubeup 1.0

Everything you set up still works. Your description defaults become the Global Default content profile and publish byte-identical on day one. Your engine settings and flows migrate on first launch. The engines have new names, but they work exactly as before. And your licence covers 2.0, because every Tubeup plan includes all future updates.

The best first hour with 2.0 is simple: open Settings and pick your AI provider (Revoye is the default), connect your other channels to the same Google project, turn your old defaults into a couple of named content profiles, then build one flow and press Simulate.

Where to go from here

If you want to see how these features fit specific workflows, like a solo creator, an agency with client channels, or a high-volume faceless operation, read our companion guide, Tubeup 2.0: YouTube Automation That Works Like an Assistant. It covers the Revoye integration and backup and restore in more depth.

New to Tubeup? It runs on Windows and macOS, every plan is a one-time lifetime licence, and you can try every 2.0 feature free for three days with no card. Everything is on the Tubeup product page.

Set it once. It publishes without you.