Instaread Audio Player — Text-to-Speech & Article-to-Audio
| 开发者 | instaread |
|---|---|
| 更新时间 | 2026年10月23日 18:13 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
标签
下载
1.2.17
1.0.3
1.2.19
1.2.9
1.2.10
1.0.4
1.2.14
1.2.3
1.0.12
1.0.13
1.0.14
1.0.2
1.0.6
1.0.7
1.0.9
1.2.1
1.2.2
1.0.5
1.1.1
1.2.4
1.2.7
1.2.11
1.2.12
1.2.13
1.2.15
1.2.16
1.2.18
1.2.20
1.2.21
1.2.22
1.2.5
1.2.8
1.0.11
1.0.8
1.1.0
1.2.0
1.2.23
1.2.24
1.2.25
1.2.26
1.2.27
1.2.28
1.2.6
1.2.29
1.2.30
1.2.31
详情介绍:
Trusted by 200+ brands and creators, Instaread Audio Player converts your WordPress articles, blog posts, and pages into natural-sounding audio and embeds an audio player on your content. The plugin is provided at no cost to publishers; Instaread operates on an ad-supported model, where revenue is generated through optional audio advertising and shared with the publisher.
The plugin is intended for publishers who want to add an audio version of their text content to improve accessibility and offer an alternative way to consume articles.
Features
- Automatic text-to-speech conversion for posts, pages, and custom post types
- Embedded audio player with waveform visualizer
- Color and style customization to match your site's branding
- Voice library with multiple natural-sounding voices; voice cloning available on request
- Site-specific pronunciation dictionary for proper nouns and brand names
- Analytics dashboard with listener metrics
- Audio podcast feed generation for distribution to podcast platforms
- Playlist support for serialized content
- Subscribe-to-listen flow for paywalled content
- Optional ad suppression for logged-in subscribers
- Works with standard WordPress themes
- Compatible with major page builders (Elementor, Divi, Beaver Builder, Gutenberg)
- Mobile-responsive player layout
- Asynchronous player loading — does not block page rendering
- Install and activate the Instaread Audio Player plugin
- Connect your site through the onboarding wizard
- Choose your voice, customize the player appearance, and add the required ads.txt lines
- Submit your site for approval
- Once approved, your articles are converted to audio and the player appears on every post
- News publishers who want to offer an audio version of their articles
- Bloggers who want to make content accessible to audio-first audiences
- Content-heavy websites looking to add audio without a separate production pipeline
- Magazine and media sites that want an audio version of their archive
安装:
- Upload the
instaread-audio-playerfolder to the/wp-content/plugins/directory, or install directly through the WordPress plugin installer by searching for "Instaread Audio Player" - Activate the plugin through the 'Plugins' menu in WordPress
- Go to Instaread in the WordPress admin sidebar — you will see the setup wizard
- Fill in your Website Name, Homepage URL, and Email Address
- Select one or more voices from the voice library (American English voices are pre-selected by default — you can preview any voice before choosing)
- Choose your Player Design (Acoustic Player is recommended), set your Player Color, and customize the player label
- Set the Player Position — "Default Position" places the player above article content automatically; "Custom Position" lets you target a specific CSS selector
- Configure Manage Posts — choose to enable audio on all posts, filter by date range, or exclude specific categories/URLs
- Click Submit for Approval — your settings are sent to Instaread for review
- Add the ads.txt lines shown on the confirmation page to your domain's
/ads.txtfile (this is required before your account can be approved) - Once Instaread approves your site, audio is generated for your articles automatically and the player appears on every post
- WordPress 5.0 or higher
- PHP 7.0 or higher
- An active internet connection (audio is generated via Instaread's cloud service)
屏幕截图:
常见问题:
Why does the player show "Audio coming soon" on my posts?
After submitting the registration form, a player placeholder appears on all your posts immediately. The placeholder changes to a fully playable audio player once Instaread approves your site and generates the audio files — this typically happens within a few hours of submission. No additional steps are needed on your end after submission.
How much does the plugin cost?
The plugin is provided at no cost to publishers. Instaread generates revenue through optional audio advertising and shares a portion with the publisher.
Do I need an API key or external account?
The plugin handles onboarding for you. Simply install, activate, and follow the setup wizard to connect your site.
What voices are available?
Instaread offers a library of natural-sounding AI voices across multiple languages and accents. Voice cloning is also available on request.
How quickly are articles converted to audio?
New content is typically converted within minutes of publishing. When you first install the plugin, your existing article archive is also converted.
Will this slow down my website?
The audio player loads asynchronously after the page has rendered, so it does not block page rendering.
Does Instaread work with my theme?
The player is designed to work with standard WordPress themes, including themes built with Elementor, Divi, Beaver Builder, and the default block editor.
Can I customize the player's appearance?
Yes. You can change colors, select from multiple player styles, and position the player where you want on the page.
I have paywalled content. Can I restrict audio access?
Yes. Instaread offers a "Subscribe to Listen" feature that restricts audio playback to subscribers or logged-in users.
Can I suppress ads for paying subscribers?
Yes. Audio ads can be suppressed for logged-in subscribers so they get an ad-free listening experience.
Who owns the audio files?
You do. Instaread stores and serves the files, but you retain full ownership. If you cancel the service, your audio files are deleted from our servers.
Do you use my content to train AI models?
No. You retain all intellectual property rights. Instaread does not use your content to train AI or machine learning models.
Does this help with accessibility compliance?
Adding an audio version of your articles can help meet WCAG and ADA accessibility guidelines by providing an alternative way to consume content for users with visual impairments or reading difficulties.
Can I distribute my audio as a podcast?
Yes. Instaread can generate a podcast RSS feed from your audio content, allowing you to distribute it to Apple Podcasts, Spotify, Google Podcasts, and other platforms.
Do you provide analytics?
Yes. You get access to a detailed analytics dashboard with listener counts, play duration, geographic data, and more.
更新日志:
1.2.31
- Improves how the audio player sits within your article layout, removing extra spacing some themes added above and below it, and gives the player disclaimer a consistent look that matches the player itself.
- Improves how the player loads on sites that use performance plugins to delay or defer JavaScript, so it appears reliably on mobile instead of waiting for the reader to tap the screen.
- Fixes an issue where the audio player could stay blank on sites that preload scripts, by making the player script's loading behaviour consistent across hosting and optimization setups.
- The ads.txt check now also looks beside your WordPress install, so sites that keep ads.txt in a subdirectory are read correctly instead of reported as empty.
- Ads Configuration: you can now check your site's live ads.txt against the entries we provide, with any differences listed line by line. Use the existing Copy or Download buttons to update the file.
- Internal: improved compatibility of the audio player script with site performance and script-delay tools, so the player begins loading with the page instead of waiting for visitor interaction. No setting changes required.
- Improved WordPress admin performance when updating previously published posts. Article notifications to Instaread are now sent in the background instead of waiting for a response.
- Fixes tag search in Content Coverage so it finds every tag on your site, not just your most-used ones. Searching now queries your site directly as you type, which matters for smaller tags such as a curated series.
- Adds a search box to the category and tag pickers in Content Coverage, so you can find an entry without scrolling long lists. Large sites now load the pickers faster, and clickable controls show the correct cursor throughout the dashboard.
- Content Coverage now supports tags. Under "Enable On Specific Posts" and "Disable On Specific Posts" you can pick tags alongside categories and URLs — useful when a series spans several categories. Your most-used tags are listed first, with post counts.
- Player designs that require account setup are now shown as unavailable in the Player Design list until they are enabled for your account, with guidance on how to request them. Also improves how publication dates are read on some themes.
- Internal: improved player-injection compatibility so the audio player renders reliably across a wider range of themes, including sites where an internal safeguard previously prevented the player from appearing on some article layouts. No configuration changes required.
- Internal: hardened the plugin's REST API. All administration endpoints now require an authenticated WordPress administrator session, and a deprecated callback route has been removed. No visible changes to the audio player or dashboard.
- Internal: updated tested-up-to metadata to align with the latest WordPress release. No functional changes.
- Internal: improved compatibility of the audio player injection with a wider range of themes and content-rendering plugins, so the player renders reliably on more single-post layouts.
- Improved Content Coverage: the Enable On Content Types list is now the single place to control where the audio player appears, with quick actions to enable everywhere or turn the player off site-wide. Also improved ads.txt verification so files managed by third-party services are recognised correctly.
- Internal: improved compatibility with sites using inline newsletter or popup blocks so the audio player renders only in the article body.
- Adds two ad-free player design options to the picker (Compact Player (Ad-Free) and Acoustic Player (Ad-Free)) for sites choosing to remove the visual ad slot; the audio pre-roll remains toggleable. Also improves the design-picker responsiveness so a design change applies on the first click, and adds clearer selected-state indicators inside the picker menu.
- The Enable On Content Types section now groups your site's content types into Primary, More, and Advanced sections so sites with many custom post types stay readable, with a warning label on framework and template content types to avoid accidental enabling.
- Improved reliability of the Enable On Content Types selection so custom post-type and Page toggles persist across the plugin's periodic sync.
- New setting to enable Instaread on Pages and other content types alongside Posts. The Manage Content section now includes an "Enable On Content Types" checkbox row where you can tick each content type your site publishes; the player and audio generation activate only on the ticked types. Your home page and blog archive pages are always excluded to keep listing pages clean. The existing "Enable On All Posts", "Specific Posts", and "Disable On Specific Posts" options automatically update their wording to reflect whichever content types you enabled — for example, ticking both Posts and Pages changes the label to "Enable On All Posts and Pages". No configuration changes required for existing sites — the previous "Posts only" behavior is preserved by default.
- Improved reliability of player placement on themes and page builders that render the article content more than once per page. In those setups, the audio player could occasionally appear twice on a single article; it now renders once regardless of how many times the theme re-renders the content. No configuration changes required — existing settings and manually-placed shortcodes are preserved.
- Player defaults refreshed: Player Color and initial waveform now default to deep navy (#134BA4), unplayed waveform to a lighter shade of the same hue (#89A5D2). Two-tone look on fresh installs. Auto-derive keeps waveforms tinted from your Player Color when you pick your brand. Show-advanced-settings toggle now shows a pointer cursor.
- Refreshed the Compact player look. The seekbar is now a full-width dynamic waveform (previously a thin range-input slider), matching the visual language of the Acoustic and Compact-Acoustic designs. Colors are driven by your existing Initial Waveform Color and Unplayed Waveform Color — no configuration changes needed. Existing customer settings and live embeds are unaffected; the change is visible in the plugin's Player Preview and in the compact design going forward.
- "View Ads.txt Content" button on the setup Submitted page now opens an in-page modal showing your ads.txt lines with a one-click Copy button. Previously the button redirected to the plugin landing page and flashed a "session expired" error, giving you no way to see or copy the content you needed to add. No navigation, no error toast — the modal stays on the current page so you can copy the lines and paste them into your ads.txt without losing setup context.
- Your dashboard now shows the current server-side value for the "Show floating player" toggle, the player background color, and the site slug. Previously these three could stay out of sync with the Instaread admin's settings until you toggled them yourself, and clicking Save could overwrite server-side changes made on your behalf.
- Your dashboard now reflects the current server-side configuration the moment you open it, so the settings you see always match what Instaread is serving. Previously, if an Instaread admin toggled a setting on your behalf, your dashboard could keep showing a stale value until your browser reloaded and clicking Save would overwrite the admin's change.
- Includes a matching backend fix that preserves fields your dashboard didn't touch. When you save one setting, unrelated fields (ads.txt content, voice rules, whitelist domains, etc.) now stay exactly as they were — even if the save only carried a subset of your configuration.
- Config changes now reflect on your site within seconds instead of hours. When you edit player position, color, or any other setting from the Instaread dashboard (or your own WordPress admin), the plugin automatically clears your page cache — WP Rocket, LiteSpeed, W3 Total Cache, WP Super Cache, NitroPack, and SiteGround Optimizer are all supported.
- Partial admin saves no longer overwrite unrelated settings. If you save a single change (e.g. just the player label), other fields you didn't touch — colors, waveform, disclaimer, voice selection — are preserved exactly as they were.
- Player Configuration now shows just the essentials by default — Player Design, Player Color, Player Label, Show "Powered by Instaread", Show audio player on posts, Show floating player. Waveform colors, timestamps color, ad text/colors, and the disclaimer settings collapse under a new "Advanced settings" toggle so first-time admins aren't overwhelmed.
- Readme cleanup: removed the "Configuration Guide" section since the Installation section already walks through the same steps.
- Minor spacing fix on the Disclaimer text color picker.
- Admin: the Instaread menu icon and plugin row now display at full color for easier identification on the Plugins and admin menu screens.
- Refreshed the Instaread icon in the WordPress admin sidebar so it's easier to spot at a glance.
- Safe upgrade. No configuration changes required; existing settings are preserved.
- Notifies the Instaread team the moment you activate the plugin so we can proactively help if you have questions during setup, and again if the plugin is later deactivated. No personal reader data is sent — only your site URL, WordPress admin email, and versions, so we know who to reach out to.
- Internal improvement: the plugin no longer inlines its layout-reservation styles on sites that haven't completed "Connect to Instaread" yet, keeping the page a little cleaner during the setup window.
- Safe upgrade. No configuration changes required; existing settings are preserved.
- Manage Posts sections now make clear you can pick just categories, just URLs, or both — sections are combined, and either alone is enough to control which posts get the player. Helpful when the posts you want are scattered across many categories.
- Refreshed the helper text under each section so the multi-select behavior (add one category or URL at a time; leave a section empty if you don't need it) is easier to follow.
- Safe upgrade. Existing configurations are preserved unchanged.
- New "Enable On Specific Posts" mode in Manage Posts: choose the categories or specific URLs where the audio player should appear. Everything outside your selection stays silent, so you can launch the player on part of your site without touching the rest.
- Manage Posts options are now ordered from broadest to narrowest reach: Enable On All Posts, Enable On All Posts Published (date range), Enable On Specific Posts (new), Disable On Specific Posts.
- Safe upgrade. Existing configurations are preserved unchanged.
- The post-setup screen now explains what happens during and after approval, so you know exactly when the audio player becomes visible on your posts.
- If you turn "Show audio player on posts" off before connecting to Instaread, the setup screen now acknowledges that readers see nothing during setup and confirms we will automatically turn the toggle back on once your site is approved.
- Safe upgrade. Copy-only change, no behavior changes.
- Improved compatibility with WordPress installations where the core files live in a subdirectory (for example WordPress hosted inside a
/wp/folder alongside other applications). The admin dashboard now reliably talks to the plugin regardless of the site's URL structure.
- Reduces the delay between Instaread approving your site and the audio player appearing. Previously the plugin had to wait for its next hourly sync cycle to notice approval; now Instaread notifies your site directly at the moment of approval so the player becomes visible within seconds.
- The audio player now activates automatically the moment Instaread approves your site — no manual toggle needed. Existing sites where the toggle was inadvertently disabled during setup are re-enabled on their next hourly sync after approval.
- Improves compatibility with popular performance, CDN, and asset-rewriting plugins (WP Rocket, Autoptimize, W3 Total Cache, LiteSpeed Cache, SiteGround Optimizer, Hummingbird, NitroPack, Swift Performance, and others) so the audio player loads reliably regardless of which optimizer is active.
- On plugin update, automatically clears the minified-JavaScript caches kept by those optimizers so the new player version is picked up without manual cache flushing.
- Future updates of this plugin are now installed automatically on your site, so reliability and compatibility improvements arrive without manual action.
- The plugin's diagnostic script now loads whenever the plugin is configured, so Instaread can detect and resolve site-specific compatibility issues even when the visible player is temporarily hidden.
- Renamed the "Show 'Audio coming soon'" toggle to "Show audio player on posts" for clarity. Behavior is unchanged for existing installs.
- Improves compatibility with popular performance, CDN, and asset-rewriting plugins (WP Rocket, Autoptimize, W3 Total Cache, LiteSpeed Cache, SiteGround Optimizer, Hummingbird, NitroPack, Swift Performance, and others) so the audio player loads reliably regardless of which optimizer is active.
- On plugin update, automatically clears the minified-JavaScript caches kept by those optimizers so the new player version is picked up without manual cache flushing.
- Future updates of this plugin are now installed automatically on your site, so reliability and compatibility improvements arrive without manual action.
- Internal: improved compatibility of the audio player script with third-party site optimization and asset-rewriting tools, so the player loads reliably across more hosting and CDN configurations. No setting changes required.
- Initial and Unplayed waveform colors now auto-derive from the Player Color as a lighter shade, so the waveform stays on-brand without extra setup. You can still pick either waveform color manually to override; once you do, future Player Color changes will not overwrite it.
- Fix: the "Show floating player" toggle introduced in 1.0.6 read as off after upgrading because the saved settings file didn't yet carry the new value. The plugin now persists the toggle through its settings store and defaults it to on for any partner who didn't have it set, matching the documented behavior.
- Added "Show floating player" toggle in Player Configuration. On by default; turn it off to disable the floating mini-player that follows readers as they scroll. The setting syncs to Instaread's external service on save.
- readme.txt: refreshed the Description opening line; condensed several sections; added a Screenshots section showing the admin setup, voice selection, player configuration, and analytics dashboards. No code changes.
- Added public-page assets (banner and screenshots) so the plugin listing is no longer placeholder art.
- Internal release tooling improvements. No user-facing changes.
- Front-end script loading: the partner JavaScript is now enqueued once in the document head (when the site administrator enables "Show Audio coming soon") instead of being emitted inline alongside each post-content slot. The post-only element continues to be injected only on single posts via the_content; non-post pages receive the script but no player markup.
- Player slot is now lighter: the per-post coordination script and placeholder loader are removed because the partner JavaScript renders its own loader and audio iframe inside the element. The reserved per-design slot height (added in 1.0.2) continues to prevent cumulative layout shift while the partner script downloads.
- External Services readme section trimmed: the endpoint URLs and short purpose lines are kept for transparency, while per-endpoint payload examples and the data-sent bullet list were removed.
- Clarified that the plugin is not Trialware/Serviceware: there is no license key check, no paid unlock, and no local plugin feature is disabled behind a payment, trial, quota, or license. The plugin connects to Instaread's external service, which performs the core functionality (article-to-audio processing, audio hosting, player delivery, ad serving, revenue-share reporting) outside of WordPress.
- Removed "Submit for approval" wording that could imply local plugin functionality is locked; the call-to-action is now "Connect to Instaread".
- Removed payment, revenue-share, and marketplace-style terms from the plugin settings screen.
- External services: added an "External Service Disclosure" section to readme.txt and an in-dashboard authorization notice describing what data is sent to Instaread and why. No new endpoints were added.
- Front-end injection is now fully admin-controlled: the partner script, wrapper markup, and player element are injected only when the site administrator enables the "Show Audio coming soon" setting; otherwise post content is returned unchanged.
- Layout stability: when shown, the player slot reserves a fixed per-design min-height (responsive desktop/mobile) to avoid cumulative layout shift; the per-post loader script is emitted inline alongside its slot for reliable loading.
- Voice selection: removed promotional tier/pricing wording from the admin UI.
- Distribution: include the unminified React/TypeScript source (react-app/src/, vite.config.ts, package.json, tsconfig.json) alongside the compiled bundle, so the plugin ships with a human-readable counterpart to the minified admin asset.
- Documentation: added a "Source Code" section to readme.txt with the build command and pointers to the source files.
- External services: disclosed the voice-metadata lookup endpoint (api.instaread.co /v1/wordpress/admin/voices/{id}) used when administrators select voices in the dashboard.
- Admin: load the React admin bundle as an ES module so the dashboard mounts correctly across modern browsers (resolves "Loading Instaread admin…" never disappearing on some sites).
- Admin: surface a clear error notice if the bundled assets are missing, instead of leaving an indefinite loading state.
- PHP 8.1+ compatibility: cast nullable post fields before string functions (strtotime, trim, preg_split, rtrim) to silence deprecation notices under WP_DEBUG.
- Hardened API response handling in voice sync against non-array payloads (array_merge type errors).
- Defensive guards around DOMXPath query results in custom-position injection.
- Initial release
- Automatic article-to-audio conversion
- Customizable embedded audio player with waveform visualizer
- Voice selection and voice cloning support
- Audio ad monetization with publisher revenue share
- Archive conversion on activation
- Analytics dashboard
- WCAG/ADA accessibility support
- Compatible with major page builders and themes