AtlasVoice Text To Speech

⌘K
  1. Home
  2. Docs
  3. AtlasVoice Text To Speech
  4. Getting Started
  5. Introduction

Introduction

Introducing AtlasVoice: The Text to Speech Plugin for WordPress & WooCommerce

AtlasVoice (Text To Speech TTS Accessibility) is a user-friendly text to speech plugin that turns any post, page, or WooCommerce product into natural-sounding audio with one click. The free version uses your browser’s built-in voices — no account, no API key, no registration. Upgrade to AtlasVoice Pro for premium AI voices from AtlasVoice’s own engine, Google Cloud TTS, OpenAI (ChatGPT) TTS, and ElevenLabs.

Whether you run a blog, news site, online store, or learning platform, AtlasVoice makes your content accessible to everyone — including visitors with visual impairments or reading difficulties, and those who simply prefer to listen. It supports 81+ languages and helps your site meet WCAG 2.1 / ADA accessibility standards.

What you get in the free version

  • 20–300+ browser voices via the built-in speechSynthesis engine.
  • The `atlasvoice` shortcode and a Gutenberg block.
  • Analytics dashboard — play counts, pause events, and engagement.
  • Text aliases for correct pronunciation of abbreviations.
  • Unlimited text to speech — no character limits or monthly quotas.
  • Full player customization, including custom CSS.
  • Custom post type support (WooCommerce, ACF, CPT UI, Toolset Types).
  • Compatible with major caching and multilingual plugins.

AtlasVoice Pro — premium AI voices

  • AI voice providers: AtlasVoice TTS Pro (included), Google Cloud, OpenAI, and ElevenLabs.
  • Bulk MP3 generation and downloadable MP3 audio.
  • Google Cloud Storage backup and JSON-LD audio schema for SEO.
  • Advanced analytics, plus 81+ languages with WPML, Polylang, GTranslate, and TranslatePress.

How it works — 3 simple steps

  1. Install & activate — the player appears automatically on your selected post types.
  2. Choose a voice — a free browser voice, or a Pro AI provider.
  3. Verify & go live — confirm what gets read with the Content Selector, then publish.

Next steps

How can we help?