Google's Free Tiers Compared: Cloud TTS vs. Translate vs. Flow

Every Google Cloud product has a free tier. What "free tier" actually means — in generosity, in usability, in whether it's enough to run something real on — varies enormously between products. I ended up relying on three of them for this project's pipeline, so here's what each one actually gives you, not what the marketing page implies.

Cloud Text-to-Speech: genuinely generous

Standard and WaveNet voices come with 4 million free characters a month; Neural2 voices get 1 million. These limits reset monthly, not daily, and they don't require a paid upgrade to keep using indefinitely — it's a permanent free tier, separate from the one-time $300 trial credit every new account also gets. For a project generating a few thousand characters of narration a week, this tier is effectively unlimited. This is the one free tier in this list I'd call unambiguously generous.

Cloud Translation API: also generous, less commonly needed

500,000 characters a month, free, permanently. If your project needs to localize a modest amount of text, this covers it comfortably. Less central to what I was building, but worth knowing it's there.

Flow (Veo 3.1): generous-sounding, capped in ways that matter

Roughly 50 credits a day — enough for a handful of short video generations. Where this one differs from the two above: it resets daily rather than monthly (so unused credits don't bank), clips are capped at 8 seconds on the free tier, and free exports carry a visible watermark. I wrote about this in more detail in an earlier post, including the commercial-use question that ultimately mattered more than the credit count.

The actual pattern

The products built primarily for developer infrastructure (TTS, Translation) had the most usable free tiers — large limits, permanent, no strings on commercial use. The product built around a hyped, resource-intensive generative model (Flow/Veo) had the most restricted one — smaller limits, daily resets, visible watermarking, and murkier commercial terms.

That's not a coincidence, and it's probably a reasonable rule of thumb elsewhere too: the more compute-expensive and hyped a "free" AI feature is, the more likely its free tier exists mainly to get you trying the paid one.

Related reading

Comments

Post a Comment

Popular posts from this blog

My OAuth Tokens Kept Expiring Every 7 Days, and the Reason Was a Dropdown Labeled 'Testing'

Three weeks into running my publishing pipeline on autopilot, it just stopped. Not with a crash -- with the exact same error I'd already spent a week debugging and fixing once before: invalid_grant: Token has been expired or revoked . Same message, same script, same working setup. I assumed I'd broken my own fix. I hadn't. This was a completely different bug wearing the same disguise, and it had been sitting there from day one, counting down. The first time I saw this error The first time invalid_grant showed up, I'd just spent days chasing a silent scheduled-publish failure that turned out to be a PowerShell file encoding bug. Once that was fixed and confirmed working for a couple of runs, I filed the OAuth error away as "collateral damage from the encoding mess" and moved on. When it came back three weeks later, with the encoding fix still verified working, that theory stopped holding up. My setup uses the OAuth installed-app flow: run the script once,...
Read more

How I Wired Up Fully-Automated Cross-Posting Between Blogger and dev.to (With Working Code)

The last two posts on this blog went out through a pipeline I built specifically so I wouldn't have to manually copy-paste content between platforms. Here's the actual setup, in case you're trying to do the same thing. The goal One command, two platforms: publish to Blogger (where this blog actually lives) and have it show up on dev.to at the same time, without dev.to's copy counting against the original for search ranking purposes. Piece 1: Blogger, via its own API Blogger still has a working API (v3), authenticated through standard OAuth — no service-account keys needed, which matters if your Google Cloud project has an org policy blocking those (mine did). A one-time browser login gets you a refresh token; after that, a script can call posts().insert() or posts().update() and posts().publish() without touching a browser again. Piece 2: dev.to, via its API dev.to exposes a simple REST API gated by a personal API key (generate one under Settings → Extension...
Read more

I Compared the Free Tiers of Google Flow, Kling AI, and Hailuo So You Don't Have To

In my last post , I mentioned pivoting away from AI-generated video after digging into the free tiers of the big three tools. Here's the actual digging — what each one gives you for free, and where the fine print gets in the way. I'm not affiliated with any of these tools. I just wanted a straight answer to "can I use this for a monetized channel without paying," and it took longer to find than it should have. The short version Tool Free credits Renewal Max clip length (free) Watermark Commercial use on free tier Google Flow (Veo 3.1) ~50 Daily 8 seconds "Made with Veo" visible Unclear — see below Kling AI ~66 Daily ~5 seconds per generation Visible Explicitly excluded Hailuo / MiniMax 200 One-time (new account bonus) ~6 seconds (768p) Visible Explicitly excluded Google Flow (Veo 3.1) Flow bundles Veo 3.1 (video), an image model, and a music model into one workspace. The free allotment is roughly 50 credits a day, n...
Read more