Urgent.News

What's breaking now, across thousands of outlets.

Tech

I Checked Google's Own Billing Console So You Don't Have To: The Real Text-to-Speech Free Tier, Voice by Voice

I went looking for one number -- how many characters of WaveNet audio I get for free every month on Google Cloud Text-to-Speech -- and found two sources that flatly contradicted each other. One search result, synthesized from several pricing-comparison sites, said the free tier was alive and generous: 4M Standard characters, 1M WaveNet, 1M Neural2, stacking every month. A second source, fetched…

Google's Text-to-Speech service has a complex pricing structure, with multiple tiers for different voice models. Initially, two conflicting sources provided information about the free tier allowance. One claimed it was 1 million characters for WaveNet and 4 million for Standard, while the other stated there was no free tier at all.

To verify these claims, I examined my own billing account through Google Cloud's console. The pricing table revealed that the free tier for Standard voices is indeed 4 million characters per month, and WaveNet, Chirp3-HD, and Studio each have their own separate 1 million-character allowance. These tiers appear to stack rather than share a pool.

Notably, the Neural2 voice type, often referenced in tutorials, was absent from the list. The absence of Neural2 pricing could indicate a rebranding or a change in the pricing model. It is crucial to verify such details directly from your own account, as pricing pages may be outdated or incomplete. Checking the billing console's Pricing tab for a filtered list of SKUs tied to your account provides a more reliable source of information.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Node.js Game Account Security: Reliable Login, Refresh, and Device Risk

Short answer: For fast game account login, balance security with short-lived access tokens, single-use session refresh, and device-risk step-ups so familiar devices resume quickly while replayed…

  • Access tokens have minimal authorization context, refresh tokens are session-specific digests
  • Device risk factors include server references, successful auth, network changes, unusual activity
  • Separate transitions for authentication, session continuation, and risk response improve reliability

More from Wednesday 26 August →