PerfLocale vs TranslatePress
A detailed, honest comparison to help you choose the right multilingual plugin for your site.
TranslatePress takes a unique approach to WordPress translation with its visual frontend editor - you translate content directly on your live site. PerfLocale takes a different path with an admin-based approach focused on performance, developer tools, and team workflows. Both are solid choices for different use cases.
Feature Comparison
| Feature | PerfLocale | TranslatePress |
|---|---|---|
| General | ||
| Price | Free, open source (GPL-2.0+) | Free core + Business from €199/year |
| Translation approach | Separate posts per language | Single post, translations stored separately |
| Open source | ✓ | ✓ (core only - Pro is proprietary) |
| Unlimited languages on free tier | ✓ | ✗ (2-language cap on free) |
| Multisite support | ✓ | ✓ (Pro only) |
| Performance | ||
| Caching architecture | 3-layer cache (static, object cache, transients) | No dedicated caching layer |
| Batch preloading | ✓ | ✗ |
| Smart query optimization | ✓ | ✗ |
| Overhead per page | <5ms | Not published |
| Translation Tools | ||
| Visual frontend editor | ✗ | ✓ |
| String translation | ✓ (scanner + file/database modes) | ✓ (frontend editor for visible strings) |
| Machine translation providers | DeepL, Google, Microsoft, LibreTranslate | Google Translate, DeepL (Pro) |
| Translation memory | ✓ | ✗ |
| Translation glossary | ✓ | ✗ |
| Translation workflow | ✓ | ✗ |
| Publish gate | ✓ | ✗ |
| Content sync (images, meta) | ✓ | ✗ |
| Content change detection | ✓ | ✗ |
| Language fallback chains | ✓ | ✗ |
| XLIFF export/import | ✓ (XLIFF 1.2) | ✗ |
| Block editor integration | ✓ | ✓ (block-sidebar include/exclude + CSS-selector rules) |
| URL and Routing | ||
| URL modes | Subdirectory, subdomain, per-domain | Subdirectory (free); subdomain/domain (Pro) |
| Self-healing URL rules | ✓ | ✗ |
| GeoIP redirect | ✓ (5 providers, extensible via filter) | ✗ |
| Automatic hreflang tags | ✓ (cached) | ✓ (SEO Pack addon, Business only) |
| SEO & Modern Web Features | ||
| hreflang in HTML head, XML sitemap, AND HTTP Link header | ✓ (all three) | Via SEO Pack addon (Business only) |
JSON-LD inLanguage + workTranslation schema enrichment | ✓ (integrates with your SEO plugin's schema) | ✗ |
| IndexNow push-indexing (Bing, Yandex, Google via Cloudflare) | ✓ (translation-aware - also pushes siblings) | ✗ |
Content-Language HTTP response header | ✓ | ✗ |
Fallback-content data-nosnippet guard | ✓ | ✗ |
| Speculation Rules prerender on language-switcher hover | ✓ (integrates with WP 6.8+ Core API) | ✗ |
| View Transitions API smooth switching | ✓ (Chrome 126+, Safari 18.2+) | ✗ |
| Integrations | ||
| SEO plugins | Yoast, Rank Math, SEOPress, AIOSEO, TSF, Slim SEO | SEO Pack addon (Business only) |
| Page builders | Elementor, Beaver Builder, Bricks, Oxygen | Auto-detected via frontend DOM |
| Custom fields | ACF, MetaBox, Pods | Auto-detected (Pro only) |
| WooCommerce | ||
| WooCommerce support | ✓ | ✓ (Business tier €199/yr) |
| Product translation | ✓ | ✓ (paid) |
| Variation translation | ✓ | ✓ (paid) |
| Attribute translation | ✓ | ✓ (paid) |
| Category translation | ✓ | ✓ (paid) |
| Inventory sync (SKU, stock, weight) | ✓ (automatic) | ✗ |
| Multi-currency with auto exchange rates | ✓ (5 providers, extensible via filter) | ✗ |
| Order emails in customer's language | ✓ | ✗ |
| Cart fragment isolation per language | ✓ | ✗ |
| Developer Tools | ||
| REST API | ✓ (full CRUD) | ✗ |
| Stateless machine-translation endpoint | ✓ (POST /block-translate) | ✗ |
| WP-CLI | ✓ (full command set) | ✗ |
| Helper API (template functions) | Fluent PHP API (perflocale()) | trp_ functions |
| Hooks and filters | 120+ | Limited |
| WordPress Abilities API (WP 6.9+) | ✓ | ✗ |
Key Differences
Translation philosophy
TranslatePress pioneered the visual frontend translation approach - you browse your live site and click on any text to translate it. This is incredibly intuitive for content editors who aren't comfortable in the WordPress admin. PerfLocale uses a traditional admin-based approach - translators work in the standard WordPress editor with a per-post Translations panel - which is better suited for developer teams, agencies, and sites with complex translation workflows.
Content architecture
TranslatePress stores translations alongside the original content in a single post. PerfLocale creates separate WordPress posts for each language, linked in translation groups. The separate-post approach gives each translation its own revision history, SEO metadata, and custom field values - but requires more database entries.
Free tier scope
TranslatePress's free version supports 2 languages and basic translation. WooCommerce support, SEO features, subdomain/domain modes, and DeepL integration require the Business plan (€199/year). PerfLocale includes all features - unlimited languages, WooCommerce, SEO integration, machine translation, and workflow - for free.
Migration from TranslatePress
PerfLocale’s bundled TranslatePress importer reads your wp_trp_* tables and reconstructs full translated post content by substituting matched strings from TP’s dictionary into the original post, then writes a brand-new post per language into wp_posts. Post translations, string translations, and translated slugs are all imported. Only reviewed translations (TP status ≥ 2) are included by default - filterable if you want auto-translated strings too. Your TranslatePress data is read-only during the import, so you can re-run or abandon safely. See the step-by-step TranslatePress migration guide for pre-flight checks, verification, and troubleshooting.
Frequently Asked Questions
Can I migrate from TranslatePress to PerfLocale?
Yes. PerfLocale includes a built-in TranslatePress importer that reconstructs translated post content from TP’s string dictionary, then imports string translations and translated slugs. Activate PerfLocale, add your languages under PerfLocale → Languages, then trigger the import from PerfLocale → Settings → Export & Import or from the CLI with wp perflocale migrate translatepress - the CLI path is recommended for larger sites because content reconstruction is the slowest part of the process. See the TranslatePress migration guide for the full walk-through.
Which is better for WooCommerce stores?
Both handle WooCommerce well. The key difference is cost: TranslatePress requires the Business plan (€199/year) for WooCommerce support, while PerfLocale includes full WooCommerce integration - products, variations, multi-currency, inventory sync, and localized emails - for free.