Frequently asked questions
Is Google Docs TTS really free?
Yes, but it is limited to basic functionality within the application. Our API offers a $0.50 free trial for 50,000 characters, valid for 7 days. After that, usage is $0.01 per 1,000 characters. We provide transparent billing via USDT, with no hidden fees or subscription requirements.
Can I use Google Docs TTS programmatically?
No, Google Docs TTS is a manual feature within the interface. Our API allows programmatic access via standard HTTP requests. You can use the official OpenAI SDKs by changing the base_url to https://api.playf65.com/v1, enabling seamless integration into your developer workflows and applications.
How many voices does Google Docs have?
Google Docs offers a limited selection of standard voices. We provide eight distinct presets, including female voices like Aria and Nova, and male voices like Felix and Atlas. Each voice is designed for specific tones, from warm narration to energetic promos, giving you more control over the output.
Is Google Docs TTS good quality?
Google Docs provides functional audio suitable for quick reading. Our API uses licensed recordings from LibriVox, resulting in natural-sounding speech. Generated files include an inaudible watermark marking them as synthetic. The quality is optimized for clarity and realism, suitable for professional indie developer projects.
Can I export audio from Google Docs?
Google Docs does not offer direct audio export. Our API returns the audio file directly in the response. You can receive formats like MP3, WAV, Opus, FLAC, or PCM. This makes it easy to integrate the audio into your apps or distribute it directly to users.
Does Google Docs TTS work offline?
No, Google Docs TTS requires an active internet connection to process text. Our API is cloud-based, requiring a POST request to receive audio. While you need connectivity to call the endpoint, the processing is roughly real-time on long texts, though short phrases may take a few seconds.
Is it suitable for commercial use?
Yes, our API is designed for commercial use by indie developers. Input text is not used for training, and generated audio is not stored. We offer a simple pricing model at $0.01 per 1,000 characters, with no monthly plans or minimum spend requirements for your business.
How does it compare to ElevenLabs?
ElevenLabs offers advanced features like voice cloning, which we do not offer. Our API focuses on reliability and a simple, cost-effective alternative. We support 23 languages and eight presets, with transparent pricing via USDT. We are not affiliated with ElevenLabs, offering a straightforward option for product teams.
What language options exist?
We support 23 languages, including English, Spanish, German, French, Japanese, and Chinese. Any voice can speak any of these languages. If the language is not specified, it is guessed from the script. We do not support Vietnamese, Indonesian, Thai, or Ukrainian.
Can I change the speed in Google Docs?
Google Docs has limited speed controls. Our API allows precise speed adjustment from 0.25 to 4.0. This gives you full control over the pacing of the audio. You can send requests via JSON body, making it easy to customize the output for different content types.
Does it support SSML?
No, our API does not support SSML. We focus on simple text input and reliable audio generation. If you need SSML, you would need to use a different provider. Our API is designed for developers who prefer straightforward HTTP requests without complex markup structures.
Is there an API for Google Docs TTS?
No, Google Docs does not offer a public API for its TTS feature. Our API is fully accessible via standard endpoints. You can use the official OpenAI SDKs by pointing them to our base URL. This allows for easy integration into your existing development workflows.
How long are the audio files?
Audio length depends on the text duration. Generation is roughly real-time, about 25 characters per second. Short phrases take a few seconds, while longer texts are split into parts and joined. Failed requests are free, ensuring you only pay for successful audio generation.
Can I clone voices in Google Docs?
No, Google Docs does not offer voice cloning. We also do not offer custom voice cloning for customers. You cannot upload your own voice or design custom voices. Our eight presets are based on licensed recordings, providing consistent, high-quality speech without the need for cloning.
Google Docs TTS Overview
Google Docs includes a built-in text-to-speech feature called "Read Aloud," accessible via the Tools menu. This native capability allows users to listen to documents directly within the browser, making it a convenient zero-cost option for quick reviews or accessibility needs without leaving the editing environment.
Built-in functionality
The feature is integrated directly into the Google Docs interface, requiring no external plugins or third-party applications. It processes text in real-time, converting written content into audible speech as you scroll, which is ideal for proofreading or passive listening during other tasks.
- Native integration within the browser
- No external software required
- Real-time conversion of text
Free access for users
Access is included with standard Google accounts, meaning there are no per-character fees or subscription tiers for the basic listening experience. Users can generate unlimited audio playback for their documents without tracking usage meters or worrying about rate limits on consumption.
Limited voice options
Unlike programmable APIs, Google Docs offers a fixed set of synthesized voices that cannot be customized via code. Users are restricted to the available presets without the ability to adjust speed, select specific tones like "warm" or "deep," or choose output formats beyond what the browser provides.
- Fixed voice selection
- No programmatic control
- Limited customization options
Limitations of Google Docs
Google Docs’ built-in reader is convenient for quick checks, but it lacks the flexibility needed for production audio. You are restricted to a fixed set of voices, but can only select one voice for the entire document, which makes it difficult to maintain a consistent tone across different sections or projects.
This rigidity becomes a bottleneck when you need to adapt audio for various use cases, such as switching from a neutral news tone to a warmer storytelling style within the same text.
Without an API, you cannot automate this process. Every read requires manual interaction, and exporting audio involves a cumbersome download step that doesn't scale for batch processing or integration into your own applications.
Single voice selection
The built-in reader offers limited voice options, and you can only select one voice for the entire document. This prevents dynamic voice changes based on content type or section.
If you need a different tone for a specific paragraph, you must manually switch voices, breaking the flow and requiring repeated user interaction.
- Only one voice per document
- No dynamic tone switching
- Limited emotional range
No API access
There is no programmatic way to access the text-to-speech engine. You cannot send a text payload and receive an audio file via HTTP.
This means you cannot integrate Google Docs’ reader into your indie app, website, or automated workflow without manual steps.
You are locked into the Google Docs interface, making it impossible to build custom audio experiences or automate content generation.
Manual download process
Exporting audio from Google Docs is a manual process. You must select the text, play the audio, and then download the file.
This does not scale well for large volumes of content or when you need to generate audio for thousands of items.
The lack of automation means higher labor costs for repetitive tasks, which is inefficient for product teams managing high-volume content.
API Alternative Benefits
Our API lets you generate audio programmatically, removing the need for manual browser interactions. You send text via a simple POST request and receive an audio file directly, enabling seamless integration into your applications without managing UI states or download prompts.
This programmatic approach ensures consistent output quality and allows you to control parameters like speed and format programmatically, ensuring the audio fits your app's exact requirements.
Unlike static browser tools, our API supports multiple distinct voices and languages. You can switch between warm narrators or energetic promo voices on the fly, giving your product a unique auditory identity without manual re-recording.
The API supports standard formats like MP3, WAV, Opus, FLAC, and PCM, making it easy to integrate with existing media pipelines. You can also adjust speech speed from 0.25x to 4.0x, optimizing audio length for different use cases.
Automate your content pipeline by triggering speech synthesis directly from your CMS or code. This eliminates manual steps, allowing you to generate audio for blogs, tutorials, or app notifications in bulk, ensuring consistent quality across thousands of items.
You can integrate our API into your existing workflows using standard HTTP requests or the OpenAI SDK, making it easy to add TTS to your product without building custom infrastructure from scratch.
Programmatic access
Our API lets you generate audio programmatically, removing the need for manual browser interactions. You send text via a simple POST request and receive an audio file directly, enabling seamless integration into your applications without managing UI states or download prompts.
This programmatic approach ensures consistent output quality and allows you to control parameters like speed and format programmatically, ensuring the audio fits your app's exact requirements.
- Simple POST request interface
- Direct audio file response
- Standard HTTP integration
Multiple voice options
Unlike static browser tools, our API supports multiple distinct voices and languages. You can switch between warm narrators or energetic promo voices on the fly, giving your product a unique auditory identity without manual re-recording.
- 8 distinct voice presets
- 23 supported languages
- Customizable speech speed
Automated workflows
Automate your content pipeline by triggering speech synthesis directly from your CMS or code. This eliminates manual steps, allowing you to generate audio for blogs, tutorials, or app notifications in bulk, ensuring consistent quality across thousands of items.
- Bulk generation capability
- CMS integration ready
- Consistent quality at scale
Cost Comparison
Google Docs TTS is free for individual users but lacks programmatic access, making it hard to integrate into automated pipelines. Our API charges a flat rate of $0.01 per 1,000 characters, ensuring predictable costs for any volume. Failed requests are refunded, so you only pay for successful audio generation.
Free vs Paid tiers
While Google Docs requires no monetary investment, it limits you to a single voice and manual downloads. Our model offers eight distinct voices and multiple audio formats (mp3, wav, opus, flac) for a consistent low price. You gain control over output quality without hidden subscription fees or per-seat charges.
- No monthly subscriptions or minimum spend
- Only $0.01 per 1,000 characters
- Failed requests are refunded automatically
Volume scaling
Scaling with Google Docs means manual effort; processing thousands of articles requires repetitive clicking. Our API handles large texts by splitting them into parts of up to 4,096 characters and joining the audio files. With 60 requests per minute, you can process substantial content quickly, paying only for what you generate.
Integration costs
Manual workflows incur hidden labor costs. By using our REST API, you automate the entire pipeline from text to audio file. The simple JSON request shape works with standard libraries, reducing development time. You avoid building custom scrapers or handling complex file management for each user request.
Use Case Differences
Google Docs TTS serves personal reading needs, playing audio directly in the browser without requiring code. It is ideal for quick reviews of documents but lacks programmatic access for automated pipelines.
Our API transforms text into audio files via simple POST requests, enabling seamless integration into apps, websites, or background services without manual user intervention.
Manual reading vs API
Google Docs offers a one-click listen feature within the interface, perfect for individual users reviewing content. In contrast, our API returns audio files (MP3, WAV, etc.) that can be stored, cached, or played by any custom player.
Manual usage requires a browser and active user interaction. API usage allows headless generation, where text is converted to audio without any human present, enabling true automation.
- Google Docs: Interactive, browser-based, single-user.
- API: Programmatic, headless, multi-user capable.
Batch processing
For batch needs, Google Docs requires opening each document individually. Our API handles up to 4,096 characters per request, allowing you to split long texts and generate audio files in parallel or sequence via code.
This approach supports high-volume workflows typical of indie product teams, such as generating audiobooks or notification sounds for thousands of users simultaneously.
- Parallel request handling.
- Automatic text splitting for long content.
- No manual document opening required.
Custom applications
With our API, you can embed TTS directly into your SaaS product or mobile app. You control the voice selection (e.g., Aria, Felix) and format based on user preferences.
Google Docs is a static tool; your API integration becomes a feature of your application, enhancing user experience with natural-sounding audio tailored to your specific use case.
- Embed audio generation in your UI.
- Custom voice and format selection.
- Dynamic content generation based on user input.
Technical Requirements
For indie developers, the API is agnostic to the client environment, delivering audio files via standard HTTP responses. This ensures consistent performance regardless of whether the consumer uses a modern browser, a mobile app, or a server-side script. The primary requirement is a stable internet connection to handle the data transfer of the resulting audio file.
Browser compatibility
The generated audio files (MP3, WAV, Opus, FLAC, PCM) are universally playable in modern web environments. Since the API returns raw audio data, integration relies on standard HTML5 audio elements or backend processing libraries, eliminating browser-specific rendering quirks common in built-in TTS tools.
Network requirements
File format support
We offer five formats: MP3, WAV, Opus, FLAC, and PCM. Choose MP3 for efficient web delivery, WAV for uncompressed quality, or FLAC for lossless storage. PCM is ideal for raw audio processing pipelines. Each format balances file size and fidelity according to your specific deployment needs.
- MP3: Best for web delivery and small file sizes
- WAV: Uncompressed, ideal for immediate playback or editing
- Opus: High efficiency for voice-only streams
- FLAC: Lossless compression for archival quality
- PCM: Raw binary data for custom processing
Data Privacy
When using our API, your input text is processed solely to generate the audio response and is never used for model training. The generated audio is delivered directly in the response and is not stored on our servers, ensuring minimal data retention.
Google data usage
Google Docs TTS relies on Google’s cloud infrastructure, meaning your document content is processed and potentially stored according to Google’s privacy policies. This can be a concern for sensitive proprietary content or strict compliance requirements.
Local processing
Our API handles synthesis remotely, but request metadata (time, character count, status) is retained briefly for billing purposes only. Unlike local TTS engines, your text leaves your device, though it is not archived for long-term analysis.
Ownership of content
You retain full ownership of the text you submit and the resulting audio files. Since we do not store the generated audio, you have immediate control over how it is distributed, embedded, or monetized without third-party claims.

Scalability
Scalability depends on your workflow. Google Docs handles single-user reading well but struggles with automation. Our API supports concurrent requests, letting you process text programmatically without manual intervention.
Manual vs Automated
Google Docs requires manual selection and download. Each file is generated individually. This works for a few documents but becomes tedious for larger projects. Our API lets you automate the entire process via code. You send text and receive audio without clicking buttons.
- Google Docs: Manual, one-by-one generation
- Our API: Programmatic, batch-ready via code
High volume needs
For high volume, rate limits matter. Our API allows 60 requests per minute per key. Longer texts split automatically. Processing takes real-time length or slightly longer under load. Google Docs has no public limits but lacks programmatic scaling.
- 60 requests per minute per key
- Automatic text splitting for long inputs
Enterprise features
We do not offer enterprise contracts, SLAs, or dedicated support lines. There are no dedicated support lines or uptime guarantees. Our model is simple: pay per character, no minimum spend. This keeps costs predictable for indie teams without enterprise overhead.
- No SLA or uptime guarantee
- No enterprise contracts or dedicated support
Developer Experience
Integration is straightforward because our API mirrors the OpenAI speech endpoint shape. Indie developers can reuse existing OpenAI SDKs by simply updating the base_url to https://api.playf65.com/v1. This means you likely already have the code structure needed to send text and receive audio files without learning a new library.
Ease of integration
Authenticating is simple: pass your API key in the Authorization header. The request body uses standard fields like model, input, voice, and response_format. You can generate audio with a single POST request and receive the file immediately, fitting seamlessly into CI/CD pipelines or backend services.
- Compatible with official OpenAI SDKs
- Standard JSON request body
- Single API key authentication
Documentation quality
Our docs provide clear examples for all supported languages and formats. You can quickly find the correct voice presets and understand character limits. The endpoint details are precise, helping you avoid trial-and-error when implementing text-to-speech features.
- Clear endpoint specifications
- Code examples included
- Voice preset details
Support availability
We offer support via email only, which is often sufficient for technical questions. There is no live chat or phone support, keeping the service lean and cost-effective for independent teams who prefer asynchronous communication.
Best for Indie Devs?
For indie developers, predictable costs and flexible integration often outweigh free but limited tools. Our API eliminates the friction of manual exports, allowing you to automate audio generation directly within your application workflows without managing infrastructure or waiting for manual processing steps.
Cost efficiency
You pay only for what you use, starting with a free trial credit. With a flat rate of $0.01 per 1,000 characters, you avoid hidden fees or subscription tiers that scale poorly as your user base grows. Failed requests are free, ensuring you only pay for successful synthesis.
- $0.50 free trial credit for 7 days
- $0.01 per 1,000 characters
- No monthly plans or minimum spend
Flexibility
Our API integrates seamlessly with standard HTTP clients and OpenAI SDKs, letting you choose your preferred tech stack. You can adjust speed, select from eight distinct voices, and choose formats like MP3 or WAV programmatically, adapting instantly to your app’s needs without UI constraints.
- Standard JSON API compatible with OpenAI SDKs
- Adjustable speed from 0.25x to 4.0x
- Support for MP3, WAV, OPUS, FLAC, PCM
Control over output
Unlike browser-based tools, you receive direct audio files with full metadata control. You can specify languages explicitly to ensure accuracy, handle text splitting for longer content, and manage audio generation entirely within your own codebase, giving you complete ownership of the generation process.
- Direct audio file response
- Explicit language code support
- Programmatic text splitting for long inputs
Final Verdict
Google Docs is ideal for personal, ad-hoc listening when you need zero setup and have minimal volume needs. It’s free and works instantly in your browser, making it perfect for quick reviews or casual reading of short documents without worrying about character counts or API keys.
Our API shines when you need to integrate speech into applications, process batches automatically, or maintain strict control over audio formats. It’s the right choice if you’re building a product, need programmatic access, or anticipate scaling beyond a few thousand characters per month.
When to use Google Docs
Use it for manual, one-off listening needs where convenience outweighs precision. It’s great for reading emails or articles on the fly without managing infrastructure.
Stick with Docs if your usage is occasional, you don’t need specific voice personalities, and you’re comfortable with the default voice and limited format options.
- No code or key management required
- Perfect for personal, low-volume listening
- Instant setup in any browser
When to use our API
Choose the API for building features into apps, automating content delivery, or requiring specific audio formats like MP3 or WAV. It offers 8 distinct voices and supports 23 languages with precise character billing.
Opt for our API when you need programmatic control, predictable pricing ($0.01 per 1,000 characters), and the ability to integrate speech generation directly into your workflow via a simple POST request.
- 8 voice presets for different tones
- Support for 23 languages
- Automated workflows via API
Hybrid approaches
You can use Google Docs for internal team reviews while using the API for customer-facing audio features. This balances ease of use with scalable, programmatic delivery.
Start with Docs to validate your content, then migrate to the API when you’re ready to automate delivery or customize the listening experience for your users.
Summary
Google Docs offers convenient, free text-to-speech for occasional reading, but lacks programmatic control and API access. Lexiconet provides a robust API for developers who need to integrate natural-sounding audio directly into their applications, supporting 8 voices and 23 languages with predictable pricing.
Choose Google Docs for quick, manual listening of documents. Choose our API for scalable, automated workflows where you need precise control over audio generation, format, and integration within your indie product’s infrastructure.
Free for small use
Google Docs TTS is entirely free for users to listen to documents in-browser. However, it is limited to a single voice, requires manual interaction, and offers no way to programmatically access or download the audio for use in other contexts.
- No API access
- Single voice selection
- Manual download process
API for scale
Lexiconet’s API allows you to send text and receive audio files programmatically. With 60 requests per minute and support for multiple formats like MP3 and WAV, it is built for automating content creation in indie applications without manual intervention.
- Programmatic access
- Multiple voice options
- Automated workflows
Choose based on needs
For occasional reading, Google Docs is sufficient. For indie developers building products that require audio features, our API offers the flexibility, pricing transparency, and developer experience needed to scale efficiently without managing infrastructure.
- Cost efficiency
- Flexibility
- Control over output
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Use PCM if you need raw samples for further audio manipulation.
23 languages
Any voice speaks any of these languages.
Sources and further reading
- Wikipedia
- Python documentation
- curl documentation
- OpenAI API reference: create speech
- LibriVox public-domain audiobooks
- LibriTTS-R paper (arXiv 2305.18802)
- LibriTTS-R corpus (OpenSLR 141)
- FFmpeg documentation
- W3C WAI: making audio and video accessible
- openai-node on GitHub
- IETF RFC 7845: Ogg Opus
- openai-python on GitHub
