Pages & posts
Every page and post, with their categories and tags. Publish or edit and the new text is translated a few seconds later.
- pt Sobre nós
- en About us
- es Sobre nosotros
Any WordPress site · WooCommerce · v0.8.6
Translate
once. Serve
from a file.
Content is translated in the background the moment you publish it. Visitors read a dictionary compiled to a file — no API on the request, no translation triggered by traffic.
/en/ English
/es/ Español
/de/ Deutsch
/fr/ Français
/it/ Italiano
/nl/ Nederlands
/pt-br/ Português do Brasil
/ja/ 日本語
/sv/ Svenska
/pl/ Polski
Any WordPress site
Not only
for stores.
WooCommerce is optional. A blog, a company site, a portfolio or a shop — if it runs on WordPress, it is translated the same way: in the background, and served from a file.
- Blogs
- Company sites
- Portfolios
- Magazines
- Landing pages
- Online stores
Works with
SEO & sitemaps
- Yoast SEO
- Rank Math
- Slim SEO
- WordPress sitemap
Works with
Page cache
- WP-Optimize
- LiteSpeed Cache
- WP Rocket
- W3 Total Cache
Works with
Store
- WooCommerce
- Official WordPress & WooCommerce translation packs
Built for stores too
The parts
others leave
in English.
The cart, the checkout, the notices — where an untranslated string hurts most, at the moment someone is spending money. Covered in three different ways, because they come from three different places.
Order emails · WooCommerce
The email arrives in the buyer’s language.
Someone buys in English. WooCommerce fires "Your order has been paid" — and the plugin sends it in English: subject, heading, product names, shipping and payment method, the date, the text you wrote for the footer. The order itself is saved in the store’s language, so the admin, the invoices and the reports read one language.
What the store wrotept-PT · the store
Subject: A sua encomenda #1042 foi paga
A sua encomenda foi paga
Olá Emma, obrigado pela sua compra. Já estamos a preparar a encomenda.
| Vestido midi em linho — Preto, M | × 1 | 49,00 € |
| Blusa de seda — Marfim, S | × 2 | 78,00 € |
| Total | 132,00 € |
Loja Mariana · Rua das Flores 12, Lisboa · Responda a este email para falar connosco.
What the buyer receivesen · the buyer
Subject: Your order #1042 has been paid
Your order has been paid
Hi Emma, thank you for your purchase. We are already preparing your order.
| Linen midi dress — Black, M | × 1 | 49,00 € |
| Silk blouse — Ivory, S | × 2 | 78,00 € |
| Total | 132,00 € |
Loja Mariana · Rua das Flores 12, Lisboa · Reply to this email to reach us.
Every email after the purchase
Paid, completed, refunded, a note from the shop — in the language of the purchase, from the subject to the footer.
Your own words, translated once
Subject, heading, additional content and footer you wrote in WooCommerce → Emails go through the dictionary. Review them by hand in Strings.
Labels for free, dates done right
"Subtotal", "Shipping", "Payment method" come from WooCommerce's human-reviewed pack. The date uses each language's own format — no "9 de September de 2026".
The shop reads one language
Orders are saved in the source language with the language of the purchase in _pht_lang. Emails to the administrator stay in the store's language.
Every order status
Processing
Paid
Completed
Refunded
Note from the shop
All in the buyer's language
Admin emails · store language
The language switcher
Any corner.
Four shapes.
Nothing for the theme to fight. Four kilobytes of CSS, only on the pages where it shows. Three shapes are plain links with zero JavaScript. Colours, size, corners and shadow are set with a live preview that warns under 4.5:1 — and every value is a CSS variable, so a theme can restyle it without !important.
AppearanceSwitcher tab
Box#ffffff
Language#1a1a1a
Current#1a1a1a
Hover#dcdcde
Text size14px
Corners8px
Shadowsoft
Contrast 16.1:1 — passes WCAG AA. The panel warns the moment a text colour falls under 4.5:1.
Where it appears
Modes01Automatic — floats in the corner you pick, nothing to touch in the theme. It also shows in the cart and the checkout, where a visitor in the wrong language needs a way back.
02Manual — place it yourself with [pht_switcher] or pht_switcher() in a template. The floating one steps aside on that page; there are never two.
03Off — hidden. Names or codes, with or without emoji flags, is a switch either way.
Suggestion bar
Optional01A visitor whose browser speaks another language sees a small bar at the top offering their version.
02It suggests, it never redirects. Redirecting by browser language breaks the page cache, and Google advises against it.
03It shows once. Choosing or closing answers for good. On translated pages the browser's own "Translate this page" offer is silenced — theirs on top of ours reads worse.
How it works
One
separation.
Translation happens in the background. Serving is read-only. It is the model Shopify uses for Translate & Adapt — and the opposite of plugins that translate HTML on demand and pay again for every new page a visitor opens.
Translation time
Background01Text is read straight from the database — products, categories, pages, menus, shop settings — plus one page of each template.
02Only what is missing goes to the PixelHunter translation service, several batches at once. A whole shop takes under a minute.
03The dictionary is compiled to a PHP file inside uploads/. A product you publish is translated a few seconds later.
Serving time
Read-only01The language prefix is stripped before the WordPress router runs — /en/shop/ resolves like /shop/. No rewrite rules.
02The dictionary sits in OPcache. Serving a translated page costs neither a query nor an HTTP request.
03HTML goes through the core WP_HTML_Processor. With an empty dictionary the output is byte for byte the input.
cost = 38 ms + 0.12 ms × replacement
linear · measured on the heaviest page of a real store · 262 KB · 719 replacements
Set-up
Four steps. One button.
There is no API account to set up and nothing to configure: the translation API holds its own key. A glossary and a brand tone are optional, under Settings.
Pricing
Pay for text.
Not traffic.
Every visit is free — only new or edited text is sent to be translated. Each character counts once per target language, and unused characters roll over while the subscription is active. Yearly plans cost ten months.
Questions about taxes, how characters are counted or changing plan? Read the plans guide in the documentation.
Straight answers
What it does. What it doesn’t.
01
Do I need an API account?
No. The plugin only talks to the PixelHunter translation API, which holds its own key — you only need the license key.
02
Do I need WooCommerce?
No. WooCommerce is optional: the plugin translates any WordPress site — pages, posts, menus, categories and the texts of your theme. When there is a store, the cart, the checkout and the order emails are covered too.
03
Are the translated pages in my sitemap?
Yes. There is no second sitemap to submit: the translated pages are added to the one you already have. With Yoast SEO, Rank Math or Slim SEO each page gets one entry per language, with all its versions as hreflang alternates; without an SEO plugin, WordPress’s own sitemap gets one sitemap per language.
04
Which plugins does it work with?
Yoast SEO, Rank Math and Slim SEO for canonicals and sitemaps; WP-Optimize, LiteSpeed Cache, WP Rocket and W3 Total Cache for page cache purging; and WooCommerce, with its official translation packs. Any other page cache can be connected through two hooks.
05
Are URL slugs translated?
No, on purpose. Only the prefix changes: /en/produto/blusas/ keeps the source slug. Each language still has its own address, with a canonical that keeps the prefix and hreflang to every other version, so Google sees language versions — never duplicate content. And a link never breaks when a translation is later fixed.
06
Does it slow my site down?
In the source language, 0 ms. On translated pages the dictionary is read from OPcache; a host page cache serves each language once per URL per TTL.
07
“Subtotal”, “Proceed to checkout”?
They come from the official WooCommerce translation pack — reviewed by humans, at no API cost. The panel says which packs are missing and installs them.
08
Do emails to the shop change?
No. Emails to the administrator stay in the store’s language; only the customer’s emails go out in the language of the purchase.
09
Requirements?
WordPress 6.7 or later and PHP 8.1 or later. No build step, no jQuery, no runtime dependencies.
10
What happens when the characters run out?
Translation pauses and retries every hour. Nothing is lost: pending texts wait for the next period, and the site keeps serving everything already translated. Need more? Change plan in My account: a new key for the new plan arrives by email, and translation resumes once it is pasted on your sites.
11
And if I cancel?
The key works until the end of the paid period. After that the site still serves every translation it has — only new text stops being translated.
12
Does staging count as a site?
Yes. Translate on the live site, or free a slot in My account → Activations while you work on the copy. The free trial is once per site and does not accept disposable emails.
13
What is not translated?
URL slugs, anything inside <script> — including SEO plugins' JSON-LD — and customer emails not tied to an order, which go out in the store's language. Each sentence has one translation across the whole site.
For developers
Three functions. Three filters. Two actions.
Current language
<?php if ( 'en' === pht_current_language() ) : ?> <p>Free shipping to the UK.</p> <?php endif; ?>
Switcher, by hand
[pht_switcher show_label="no" class="mine"] <?php pht_switcher( [ 'style' => 'dropdown' ] ); ?>
Any page cache
add_action( 'pht_purge_urls', function ( $urls ) {
foreach ( $urls as $url ) my_cache_purge( $url );
} );