Translate WordPress with GTranslate vs MediaBlaster – Video CMS, IPTV, Podcasts & Streaming Toolkit

Translate WordPress with GTranslate plugin uses Google Translate AI translation service to translate wordpress site with Google power and make it multilingual. With 103 available languages your site will be available to more than 99% of internet users. Our paid versions are fully SEO compatible which will increase your international traffic and sales. This translate plugin is a budget multilingual WordPress solution which combines automatic and human translations to save money and is easy to implement. GTranslate is a leading website translation services provider since 2008, it moves away the language barriers. Compared to other translation plugins for WordPress, we use cloud based approach which does not slow down your website. In addition to that, we can offer complete SEO features based on sub-domains with our paid options, which can make your website appear in search engines in different languages which will increase your international traffic and sales. In our paid versions we DO NOT limit the number of words or the number of translated pageviews. You DO NOT pay additionally for automatic translations. Please use GTranslate Support for your questions and support requests! We are multilingual! Please check our FAQ to get quick answers. Features Free Google automatic machine translation Hides Google top frame after translation Translate website on the fly Translate posts and pages Translate categories and tags Menus and widgets translation Themes and plugins translation Right to left language support Google language translator widget Auto-switch language based on browser defined language Available styles Float, Dropdown, Flags, Flags with dropdown, Nice dropdown with flags, Flags with language names, Flags with language codes, Language names, Language codes, Globe, Popup Floating language selector WooCommerce shop translation Multilingual language names in native alphabet Alternative flags for Quebec, Canada, USA, Brazil, Mexico, Argentina, Colombia Lazy loading for language flags and js libraries to boost performance Lightweight vanilla javascript without dependencies Forum Support Paid Features Multilingual SEO – Enable search engine indexing Neural machine translations with human level translation quality Increase traffic and AdSense revenue Search engine friendly (SEF) URLs Yoast SEO compatible – translate meta keywords, meta description, schema.org data structures, translate sitemaps WooCommerce compatible – translate products, schema.org data structures You can have sub-directory (example.com/es/) or sub-domain (es.example.com) URL structure URL Translation aka slug translation is possible (example.com/about-us → example.es/sobre-nosotros) Add hreflang tags for translated alternatives You can manually correct translations In context translation interface (make corrections without losing the context) Meta data translation (meta keywords, meta description) Translating schema.org microdata for better search engine appearance Seamless updates (cloud service updated on our side – SaaS, you do not need to worry about backups on your side) JSON format translation Translate WooCommerce emails AMP translation (Accelerated Mobile Pages translation) Image localization – Media translation Translation Proxy (aka Translation Delivery Network) Centralized Translation Cache – We revise and improve translations over time Language Hosting (example.fr) User Dashboard with Analytics Live Chat Support See also If you are looking for unlimited, high-quality automatic translations, check out TranslateX – an automatic translation API offering unlimited translation for your website or application. We also offer integration plugins: TranslateX for Loco Translate – integrate TranslateX API directly into Loco Translate for seamless, unlimited automatic translations. TranslateX for TranslatePress – bring unlimited automatic translation to TranslatePress using TranslateX API. These solutions make it easy to supercharge your WordPress multilingual setup with TranslateX’s secure and affordable API. GTranslate WordPress Demo Watch GTranslate Tour Edit Translations Demo (paid)

MediaBlaster is the next evolution of WP Smart TV. Originally launched as WP Smart TV, the plugin helped WordPress users create IPTV-style video feeds for platforms like Roku Direct Publisher. Roku Direct Publisher is discontinued, and the live Roku JSON feed has moved to the separate WP Smart TV – Legacy plugin (https://github.com/rovidxmedia/wp-smart-tv-legacy). MediaBlaster is the forward path for video CMS, players, podcasts, subscriptions, and the /wp-json/mediablaster/v3/ REST API. That is why WP Smart TV has been renamed and rebuilt as MediaBlaster. MediaBlaster is a WordPress-powered media CMS for creators, publishers, educators, filmmakers, podcasters, and businesses that want to organize, publish, and monetize video and audio content from one central place. Use it to build: Video libraries IPTV-style content catalogs Podcast and episode archives Membership-based media sites Headless WordPress media backends Custom video websites Roku, mobile, TV, or web app content sources AI-assisted media brands and creator platforms Learn more at mediablaster.io. Join the MediaBlaster creator community on Skool. WP Smart TV is now MediaBlaster If you previously used WP Smart TV, this is the same plugin project moving forward under a new name. The name has changed because the plugin is no longer focused only on “smart TV” or Roku Direct Publisher workflows. MediaBlaster is designed for the broader media publishing landscape: web video, Vimeo libraries, podcasts, subscriptions, headless WordPress, custom apps, and creator-led media platforms. Important notes for existing users: Existing WP Smart TV content remains supported. Existing video post types and metadata are preserved where possible. The user-facing name is now MediaBlaster. The live Roku Direct Publisher REST feed (/wp-json/tv/roku/) and legacy /wp-json/wpst/v1/ routes are not registered in 3.0.0. Roku Direct Publisher admin screens (Roku Settings, Recipes, feed export) have been removed from MediaBlaster. If you still need a Roku Direct Publisher JSON feed, use the separate WP Smart TV – Legacy plugin: https://github.com/rovidxmedia/wp-smart-tv-legacy New development is focused on MediaBlaster as a modern WordPress media platform (REST API, players, podcasts, subscriptions). Key Features Video CMS for WordPress MediaBlaster adds structured media content management to WordPress, allowing you to organize video content using dedicated media post types and metadata. Manage: Movies Episodes Series Short-form videos Video metadata Thumbnails Captions HLS and MP4 video URLs Vimeo-connected media Legacy video metadata (captions, trickplay, ad breaks) when Legacy Controls are enabled MediaBlaster Player MediaBlaster includes a modern HTML5 video player powered by Video.js with a native fallback. Embed methods (all use the same PHP renderer): Shortcode [mediablaster_player] (legacy alias: [tv-video-player]) Gutenberg block mediablaster/player Elementor widget (when Elementor is active) Features include HLS/DASH/MP4 playback, captions and chapter tracks, subscription-aware locked states, and post-backed source resolution from MediaBlaster video meta. Vimeo Integration Vimeo integration is built into the core plugin but disabled by default. Enable it under MediaBlaster → General Settings → Enable Vimeo Integration. MediaBlaster supports creators and publishers using Vimeo Pro, Business, or other Vimeo-hosted libraries. Features include: Vimeo OAuth connection flow Vimeo video URL support Vimeo metadata syncing Thumbnail importing HLS video URL support where available Tags, titles, and descriptions Guided Vimeo Mass Import workflow Review-before-import process This replaces the older separate Vimeo Extender workflow and brings Vimeo support directly into the core plugin. Modern Vimeo Mass Importer The Vimeo Mass Importer has been redesigned to make importing large video libraries easier. The new importer includes: Cleaner card-based interface Import readiness status Review & Import step Collapsed advanced settings Loading and progress states Better error handling Simpler workflow for non-technical users Podcast & Episode Publishing (Beta) Podcast support is built into MediaBlaster but disabled by default. Enable it under MediaBlaster → General Settings → Enable Podcasts. When enabled, MediaBlaster adds: Podcast Shows and Podcast Episodes custom post types Per-show RSS feeds (Apple Podcasts / Spotify-compatible) Public show and episode pages (optional) Podcast Settings tab (RSS bases, public URLs, premium teasers when subscriptions are on) REST API at /wp-json/mediablaster/v3/podcasts Podcast Audio Player — shortcode [mediablaster_audio_player], Gutenberg block mediablaster/audio-player, Elementor widget, and default episode templates Podcast features are in beta and may change in future releases. Subscription Foundation MediaBlaster includes a subscription and entitlement foundation for publishers who want to restrict access to premium content. Subscription features include: Subscription tiers Access groups Manual subscriber management Subscriber access rules Subscription-aware video and podcast content controls REST API auth and subscriber status endpoints Shortcodes for subscribe/account workflows Subscriptions are disabled by default. Enable early access by adding define( 'WPST_SUBSCRIPTIONS_ENABLED', true ); to wp-config.php, then configure under MediaBlaster → Subscriptions. Stripe Checkout Support MediaBlaster includes early Stripe Checkout support for web-based subscriptions. Stripe features include: Stripe hosted checkout Stripe billing portal Tier-to-Stripe Price ID mapping Stripe webhook handling Subscription sync tools Stripe checkout shortcode Public subscription app configuration endpoint (GET /app/config) Additional payment provider support is planned for app and platform-based payment workflows. App Config MediaBlaster includes a platform app configuration system for connected TV and mobile clients. Admin: MediaBlaster → App Config (under General Settings) with an App Settings tab (additional platforms planned) Public REST: GET /wp-json/mediablaster/v3/config?platform=roku Configure branding colors (color picker + custom hex), fallback hero/poster images (URL, pkg: path, or Media Library), navigation features, labels, home layout, and boot behavior Saved settings merge with sensible defaults; homeRows returns [] in v1 Distinct from subscription GET /app/config (Stripe and auth client settings) REST API for Headless and App Builds MediaBlaster includes a modern REST API foundation under: /wp-json/mediablaster/v3/ This API is designed for: Headless WordPress sites Custom front ends Mobile apps Roku apps TV apps AI-generated front ends Subscriber-aware media apps The goal is to make WordPress the content hub while allowing developers and creators to build whatever front end they need. Legacy WP Smart TV Compatibility MediaBlaster preserves existing WP Smart TV content and metadata, but does not serve the Roku Direct Publisher REST feed in 3.0.0. Removed in MediaBlaster 3.0.0: Live Roku Direct Publisher feed at /wp-json/tv/roku/ Legacy REST namespace /wp-json/wpst/v1/ Roku Direct Publisher admin screens (Roku Settings, Recipes, feed export UI) Still available in MediaBlaster: Existing video post types, rovidx_smarttv_* meta, and series structures Optional Legacy Controls on General Settings (trickplay/BIF, subtitles, advanced fields, advertising metaboxes) Roku JSON import logic (internal; admin Import/Export tab removed — use REST API or the legacy plugin for feed output) Internal Roku feed builder class (for compatibility hooks only; not registered as a public REST route) Need a Roku Direct Publisher JSON feed? Install the open-source legacy plugin maintained separately: https://github.com/rovidxmedia/wp-smart-tv-legacy That plugin (WP Smart TV – Legacy, v2.3.0) continues bug-fix support for Roku Direct Publisher workflows. MediaBlaster 3.0.0+ is the forward path for REST API, players, podcasts, and subscriptions. Shortcodes MediaBlaster includes shortcodes for displaying and interacting with media content inside WordPress pages and posts. Available shortcodes include: [mediablaster_player] / [tv-video-player] — video player [mediablaster_audio_player] — podcast audio player (podcasts enabled) [wpst_subscribe] / [wpst_stripe_checkout] — Stripe checkout (subscriptions enabled) [wpst_account] — subscriber account and billing portal (subscriptions enabled) Shortcode availability depends on which features are enabled. Built-in Documentation MediaBlaster includes in-plugin documentation inside WordPress admin. Look for: MediaBlaster → Docs Documentation may include setup guides for: App Config (Roku and platform app settings) Vimeo integration Subscriptions Stripe Checkout REST API usage MediaBlaster Player and Podcast Audio Player Podcast publishing Developer references Vimeo, podcast, and subscription guides appear only when those features are enabled. Who MediaBlaster Is For MediaBlaster is built for: Video creators Podcasters Course creators Filmmakers Churches and ministries Educators Local media companies Niche streaming publishers AI content creators Agencies building media websites for clients Developers building custom app front ends Businesses that want a branded media library If you want WordPress to act as the hub for a media-driven website, video platform, podcast network, or custom streaming app, MediaBlaster is built for that direction. What MediaBlaster Is Not MediaBlaster is not a video hosting service. You still need to host your media files with a proper video host, CDN, Vimeo account, cloud storage provider, or other media delivery system. MediaBlaster helps you organize, manage, display, structure, and publish your media from WordPress. Recommended Media Hosting MediaBlaster works best when paired with a dedicated media hosting solution. Common options include: Vimeo Bunny.net Cloudflare Stream Amazon S3 and CloudFront Wasabi Custom HLS hosting Other CDN-backed media storage YouTube is generally not recommended for direct video feed workflows because YouTube does not provide the direct HLS or MP4 URLs required for many custom video player and app workflows. Getting Started After activating MediaBlaster: Go to MediaBlaster → General Settings. Choose which media features you want to enable (post types, Vimeo, podcasts). If using Vimeo, enable Vimeo Integration and connect your Vimeo app. If using podcasts, enable Podcasts and configure Podcast Settings. Add or import your video or podcast content. Review your content metadata. Use MediaBlaster shortcodes, templates, or REST API endpoints to publish your content. Visit MediaBlaster → Docs for setup guides. Roadmap MediaBlaster is being developed as a broader media publishing system for WordPress. Planned areas of focus include: Podcast publishing improvements (currently in beta) More REST API endpoints Improved headless front-end support Better subscription workflows Additional payment provider support Better app-focused content delivery Creator and agency documentation Example front-end builds Tutorials for building custom MediaBlaster themes and apps Join the community to follow development, ask questions, and help shape the roadmap on Skool. Developer Notes MediaBlaster is designed to support both traditional WordPress sites and headless WordPress builds. Developers can use the MediaBlaster REST API (/wp-json/mediablaster/v3/), custom post types, metadata, and WordPress theme system to build custom media experiences. For Roku Direct Publisher JSON feeds specifically, use the legacy plugin at https://github.com/rovidxmedia/wp-smart-tv-legacy. For custom Roku channels or other apps, consume the MediaBlaster v3 REST API. Potential use cases include: Custom WordPress themes Next.js front ends React Native apps Roku apps Expo mobile apps TV-style interfaces Subscriber-only media portals AI-generated content sites Niche streaming networks Support For documentation and updates, visit mediablaster.io. For community discussion, tutorials, and creator workflows, join us on Skool. License MediaBlaster is licensed under the GPL v2 or later. See: https://www.gnu.org/licenses/gpl-2.0.html