VoiceX – Text to Speech Reader
| 开发者 | wpxero |
|---|---|
| 更新时间 | 2026年11月8日 11:42 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-3.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- Activate VoiceX. A Listen player appears on your single posts straight away.
- A visitor presses Listen. Their browser reads the title and the article, one sentence at a time, in the most natural voice their device has for your language.
- They can pause, resume, stop, and (if you allow it) pick a voice and a speed.
- Works out of the box – the player appears on single posts as soon as the plugin is active. Turn on pages and other public content types with one checkbox.
- Natural voices first – picks the most natural-sounding voice on each device (neural and online voices first) and never uses novelty voices. Set a preferred voice, speed and pitch if you like.
- Accessible player – real buttons with visible focus, full keyboard support, status announcements for screen readers and 44 px touch targets.
- Play, pause, resume and stop, with optional voice and speed choices for visitors. Their choice is remembered in their own browser.
- Two layouts – Standard (controls in a panel) or Button only (a single Listen button).
- Placed automatically or by hand – before or after the content, with the VoiceX Player block, the
[wpxero_text_to_speech]shortcode or the Elementor widget. The shortcode also works in Divi, Bricks and other page builders. - Per-post control – hide the automatic player on any post from the block editor panel or the classic editor box.
- Reads only the article – skips scripts, navigation, forms, hidden elements and the player itself. The title can be read first.
- Handles long articles – reads one sentence at a time, so browsers don't stop part-way, and pauses cleanly when a phone locks or the tab goes to the background.
- Multilingual – reads any language the visitor's device has a voice for. With Polylang or WPML, each post is read in its own language.
- Clear settings screen – a setup checklist and a live preview that plays your unsaved changes.
- Lightweight and cache-friendly – one small script and stylesheet, loaded only on pages with a player. React is used only in the admin screen.
- Private by design – no tracking, no cookies, no visitor data on your server.
- Translation-ready – every interface string can be translated.
- General – turn automatic insertion on or off, choose content types, and place the player before or after the content.
- Player – choose the layout and which controls visitors get.
- Voice and playback – reading language, preferred voice, default speed and pitch.
[wpxero_text_to_speech]
Optional attributes:
layout–standardorbutton(extensions may add more)title–yesorno: read the post title firstlang– a language code such asen-GBrate– speed from0.5to2
[wpxero_text_to_speech layout="button" title="no" rate="1.25"]. Invalid values are ignored and the settings are used instead. A post that contains the block or shortcode does not also get the automatic player.
VoiceX Pro
Everything above is free. VoiceX Pro is an optional paid add-on that adds sections to the same VoiceX screen:
- Natural AI voices – every visitor hears the same studio-quality voice, on any device and with the screen locked. Connect your own OpenAI, ElevenLabs, Google Cloud or Microsoft Azure account; each post is recorded once and played from your site.
- Podcast feed – publish your recordings as a podcast for Apple Podcasts and Spotify.
- Listening stats – plays and listens to the end per post, counted on your site without cookies.
- Read-along highlighting – the sentence (and, where the voice supports it, the word) being read is highlighted.
- Listen to a selection – visitors select a passage and hear just that part.
- Nine more player designs – Studio (a podcast card with cover art, seek bar and skip buttons), Capsule, Editorial, Waveform, Glass, Midnight, Expanded, Compact and Minimal, with your own colours and labels, plus a floating mini player.
- Content rules – place the player after any paragraph, choose what is read, and skip posts by category, tag or length.
- Per-post settings, WooCommerce product pages and settings import/export.
- Optional opt-in – nothing is sent unless an administrator chooses "Opt in" on the VoiceX Overview screen. If they do, Freemius receives the administrator's name and email address, the site address, the WordPress, PHP and plugin versions and, if allowed, the list of plugins and themes, to send security and feature-update notices and non-sensitive diagnostics. You can opt out at any time from the plugin's row on the Plugins screen.
- VoiceX Pro licensing – buying, activating and updating VoiceX Pro happens through Freemius.
build/ folder are compiled. Their human-readable source (TypeScript, React and SCSS in src/), build configuration and tests are public at github.com/WPXERO/wpxero-text-to-speech.
To rebuild the files, use Node.js 22.22 or later and run npm install and then npm run build in the plugin's source directory. The build uses @wordpress/scripts (webpack).
安装:
- In your dashboard, go to Plugins › Add New, search for VoiceX, then install and activate it. Or upload the ZIP file there.
- You land on the VoiceX Overview, with a live preview of the player. Press Listen to try it.
- Open any single post: the player is already shown before the content.
- Optional: under VoiceX, choose content types, placement, layout, voice and speed.
屏幕截图:
![The [wpxero_text_to_speech] shortcode in a Shortcode block.](https://cdn.jsdelivr.net/wp/wpxero-text-to-speech/assets/screenshot-4.png)
常见问题:
Is VoiceX free?
Yes. The text to speech player, automatic and manual placement, both layouts, the voice and speed settings and the accessible controls are free, with no usage limits. VoiceX Pro is an optional paid add-on.
Do I need an API key or a paid speech service?
No. VoiceX uses the speech voices built into each visitor's browser and device. There is nothing to sign up for and no usage cost.
How do I add a "Listen" button to my WordPress posts?
Activate VoiceX: the button appears on single posts automatically. To place it somewhere specific, add the VoiceX Player block, the [wpxero_text_to_speech] shortcode or the Elementor widget where it should appear.
How do I add text to speech to pages or custom post types?
Go to VoiceX › General and tick the content types under Content types. You can also place the block or shortcode on any page by hand.
How do I hide the player on one post?
In the block editor, open the VoiceX panel in the post sidebar and turn off Show the automatic player. In the classic editor, untick it in the VoiceX box.
Which voice will visitors hear?
The preferred voice set under Voice and playback, if their device has it. Otherwise the most natural-sounding voice for the reading language on their device (neural and online voices first; novelty voices are never picked), then the best voice in the device's own language. Voices differ between devices; VoiceX Pro can give every visitor the same AI voice.
Can I use AI voices such as OpenAI or ElevenLabs?
Yes, with VoiceX Pro. Connect your own OpenAI, ElevenLabs, Google Cloud or Microsoft Azure account; each post is recorded once and every visitor hears the same natural voice. Your provider bills you directly, with no extra per-character fee.
Which languages are supported?
Any language for which the visitor's device has a voice. The reading language defaults to your site language; change it under Voice and playback, per player with the shortcode's lang attribute, or let Polylang or WPML set it for each post.
Does it work with WooCommerce, Elementor, Divi or the classic editor?
Yes. Use the Elementor widget, or the shortcode in Divi, Bricks and other builders, and the VoiceX box in the classic editor. The player on WooCommerce product pages is part of VoiceX Pro.
Will it slow down my site?
No. The player is one small script and stylesheet, loaded only on pages that show it, and the speech runs in the visitor's browser. It works with page caching.
Can visitors choose the voice and speed?
Yes, if you allow it under Player › Visitor controls. Their choice is remembered in their own browser only.
Is VoiceX a screen reader? Does it make my site accessible?
No to both. Screen-reader users keep using their own screen reader; VoiceX is for everyone who prefers to listen. It supports your accessibility work but does not by itself make a site meet WCAG or any law.
The player says "There is no text to read here"
The automatic player reads the element it is placed in. Some themes put the article text somewhere else; place the block or shortcode inside the content instead.
What happens without JavaScript or speech support?
The player stays hidden until its script runs, so there are no buttons that do nothing. In browsers without speech support the player says so.
Does the plugin collect or send personal data?
Not about your visitors: the player makes no external requests and stores nothing about them on your server. A visitor's voice and speed choice is kept in their own browser. For the site administrator, the only data sharing is the optional Freemius opt-in described under External services.
What happens to my settings when I deactivate or delete the plugin?
They are kept, so you can reactivate later. To remove them when deleting the plugin, turn on Delete settings when the plugin is deleted under General.
更新日志:
- First release: a free text to speech Listen player for posts, pages and custom post types.
- Automatic placement before or after the content, the VoiceX Player block, a shortcode and an Elementor widget.
- Natural voice selection that never uses novelty voices, with optional visitor voice and speed choices.
- Accessible controls, sentence-by-sentence reading and clean pausing on mobile.
- Polylang and WPML support, a classic editor box and a settings screen with a live preview.