Support Log in

AI Credits — How They Work

User Guide
Prefer video? Watch the Lang Forge tutorials 9 short guides covering every feature Watch

All AI-powered features in Lang Forge — single post translation, bulk site translation, string translation, re-translation of out-of-date posts, and per-segment translation in the Visual Editor — draw from your account’s credit balance. Understanding how credits work helps you plan your translation budget and avoid running out at a critical moment.

Credits are a pay-as-you-go system. Plans are license-only — they do not include any recurring credit allowance. The first activation of a paid Forge license on your account (any product, any tier) grants a one-time welcome bonus. Subsequent purchases, upgrades, and renewals do not re-trigger this grant — it lands once per account, ever. When you need more, you buy credit packs that never expire and roll forward indefinitely. Each AI action costs a certain number of credits based on the volume of content being processed, and you see the estimated cost before confirming.

What your plan includes

PlanSitesAI credits granted by the plan
Personal (any single plugin)1 site—
Professional (any single plugin, 5 sites)5 sites—
Agency (any single plugin, unlimited)Unlimited sites—
Bundle Single1 site (all 4 plugins)—
Bundle Professional5 sites (all 4 plugins)—
Bundle AgencyUnlimited sites (all 4 plugins)—

Plans grant zero credits on their own. The welcome pack — a one-time grant of credits — is triggered separately by the first activation of a paid Forge license on the account (whether that’s a single Lang Forge Personal license, a Field Forge Agency license, or the full Forge Suite Bundle). It lands once per account, ever, so a second purchase on the same account does not bring another welcome pack. From there on, top up with pay-as-you-go credit packs (see avakode.com/pricing for current pack sizes). Packs are shared across all Forge plugins on the account.

How credit costs are calculated

Credit usage depends on the amount of content being translated. Segment/string translation starts at 1 credit; full post translation starts at 3 credits. Longer posts or posts with many custom fields can use more credits through the oversized-token surcharge. A text that has an exact match in Translation Memory is taken from the memory and is not sent to the AI, so it uses no credits.

Content typeTypical credit cost
Short segment/string translation1+ credits
Standard post translation3+ credits
Long article or page with many custom fields3+ credits plus token surcharge if needed
WooCommerce product (name + descriptions)Priced as a post: the credit badge of the button
Batch of 100 theme/plugin stringsEstimated before confirmation
AI re-translation of an out-of-date translation (the whole post)Estimated before confirmation

Step-by-step: Monitoring and managing your credits

  1. Look at the credit chip in the header of any Lang Forge screen in your WordPress admin. It shows your remaining credits out of your total, and it appears once the site is connected to your Avakode account and the Pro license is active. Click it to open a panel with:
– Your current credit balance

– Your add-on credits, and a note that credits never expire

– A Refresh button

– A Buy credits button that opens the pack picker. Select a pack and click Proceed to checkout to open the Paddle checkout for that pack in a new tab

  1. For the credits used in the last 30 days, grouped by AI action, open avakode.com/dashboard/credits. Your license is under Lang Forge > License
  1. The screens that start a larger run show its cost first: the strings page and the Visual Editor open a dialog with the cost of the run, and Duplicate + AI Translate shows the Estimated Translation Cost with Proceed and Cancel. The AI Translate button of a post carries a credit badge with the price and asks you to confirm before it overwrites the translation. Comment translation, once you turn it on, uses credits when a visitor opens a comment in another language. Your remaining balance is in the credit chip in the header of every Lang Forge screen
  2. Credits never expire. Your balance rolls forward indefinitely — unused credits stay in your account until you spend them
  3. Credits are deducted only after the AI has returned a translation, so a request that fails on the service is not charged
  4. All AI features share the same credit pool — single post translation, bulk translation, string translation, re-translation of out-of-date posts, and per-segment Visual Editor translation all draw from the same balance. Credits are shared across every Forge tool that uses AI

What happens when you run out of credits

If your credit balance reaches zero, AI translation buttons become disabled across the interface until you top up. Purchase an add-on credit pack at any time for immediate use:

Pay-as-you-go credit packs are listed on avakode.com/pricing — pick the size that matches your expected usage. Packs scale from small (trial one project) to bulk (multi-site launches), with better per-credit rates at larger sizes.

All packs never expire — unused credits roll forward indefinitely, even across billing cycles. Packs are purchased at avakode.com/dashboard/credits or directly from the credit chip in your WordPress admin header.

Real-world example: Planning credits for a site launch

You are launching a German version of your business website. The site has 80 pages and 60 blog posts. Based on the content length, the plugin shows you the estimated total cost before starting. If this is your first paid Forge license, the one-time welcome bonus covers a chunk of it; top up with a pay-as-you-go pack to sustain the launch and leave a comfortable buffer for subsequent content updates, string translations, and re-translations of out-of-date posts. Because pack credits never expire, any leftover balance stays available for next quarter’s work.

Common mistakes to avoid

  • Starting a large bulk translation without checking your balance. The bulk operation stops mid-way if credits run out, leaving some posts untranslated
  • Forgetting that Translation Memory saves credits. Use Translation Memory actively: a text that has an exact match in the memory is not sent to the AI, so a repeated text uses no credits
  • Buying a single small pack for a huge one-time project. For large launches, a larger pack works out to a much lower per-credit rate than stacking multiple small packs — see avakode.com/pricing for the rate ladder

> Tip: If you are planning a large translation project (like translating your entire site into a new language), check the estimated credit cost before starting: click Duplicate + AI Translate in the One-Click Site Duplication card on Lang Forge > Tools, and the panel shows the estimate before anything runs. If it exceeds your current balance, purchase an add-on pack in advance to avoid interruptions.

> Good to know: Before the AI Translate button of a post, a bulk run or the Visual Editor sends a text to the AI, Lang Forge looks for an exact match in your Translation Memory: the same source text for the same pair of languages. When it finds one, it uses the stored translation and no credits are deducted for that text. Translation Memory finds a text only when it has no HTML tags (a title, an excerpt or a string usually has none); a paragraph in the Visual Editor and the text of a post come with their tags, so they are not found. Re-Translate All, on the strings page and in the Visual Editor, skips the memory, and a bulk run uses it only when the title, the text and the excerpt of a post all have a match (an empty excerpt needs none). If a translation of a post fails halfway, the parts that already came back are kept for one hour, so a second try asks the AI only for the parts that failed.

[Screenshot: The credit chip in the Lang Forge admin header, opened to show the credit balance, the Refresh button, and the Buy credits button]

—

Forge AI Assistant Online

Hi! I'm the Lang Forge AI assistant. Ask me anything about the plugin — setup, features, troubleshooting, or development.

Just now
Powered by Forge AI · Browse docs