Usage and spend

This page is about what your DeepL or Google account gets billed. It is not your LocalePro price. Need the key itself? Connect DeepL or Google.

The Usage and limits tab under LocalePro → Settings is where that spend is watched and capped.

A monthly limit

Set a ceiling on how many characters may be sent to DeepL or Google in a calendar month. At zero (the default) there is no limit. Once one is set:

• Under 80%, nothing changes.
• From 80% to 100%, a warning shows on every LocalePro screen, and in Site Health.
• At 100%, new translating pauses. Everything already saved keeps being served. Sentences that would need a new call stay in your language, until the month ends or you raise the limit.

The point is the bad day, not the normal one. A crawler that finds ten thousand untranslated pages in an afternoon is a real bill. A limit is what keeps that from becoming your bill before you know it happened.

This month

Below the limit, a table shows what has been sent to each service this month: characters, sentences, and requests. It resets at the start of each calendar month. This is the number that becomes a line on your DeepL or Google invoice. Anything already saved costs nothing to keep showing.

Staging and local copies

Outside production, LocalePro does not call DeepL or Google at all, unless you say so. A staging copy of the database carries the same keys as the live site, and the first page load there would otherwise bill the live account for sentences nobody else will read. Turn on Allow provider calls outside production only for a copy that is genuinely meant to spend.

A line in wp-config.php does the same thing, if you’d rather not store that choice in the database:

define( 'LOCALEREADY_ALLOW_PROVIDER', true );

Saved translations are always served, on any copy of the site. Only new calls are held back.