All AI-powered features in Lang Forge — single post translation, bulk site translation, string translation, AI updates for content diffs, 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 simple, predictable pay-as-you-go system. Plans are license-only — they do not include any recurring credit allowance. Your first-ever paid Forge purchase on an account (any product, any tier) grants a one-time welcome pack. 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 always see the exact cost before confirming — so there are no surprises.
What your plan includes
| Plan | Sites | AI 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 Single | 1 site (all 4 plugins) | — |
| Bundle Professional | 5 sites (all 4 plugins) | — |
| Bundle Agency | Unlimited sites (all 4 plugins) | — |
Plans grant zero credits on their own. The welcome pack — a one-time grant of credits — is triggered separately by your first-ever paid Forge purchase 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. Posts with Translation Memory exact matches use fewer credits because matched segments are free.
| Content type | Typical credit cost |
|---|---|
| Short segment/string translation | 1+ credits |
| Standard post translation | 3+ credits |
| Long article or page with many custom fields | 3+ credits plus token surcharge if needed |
| WooCommerce product (name + descriptions) | Estimated before confirmation |
| Batch of 100 theme/plugin strings | Estimated before confirmation |
| AI update for a content diff (changed segments only) | Estimated before confirmation |
Step-by-step: Monitoring and managing your credits
- Go to Lang Forge > Account in your WordPress admin to see your credit dashboard
- The dashboard shows:
– Credits spent to date
– Usage history (a list of recent AI actions with their credit costs)
– A Buy credits button that opens the pack picker
- Before every AI action (whether single-post translation, bulk translation, or string translation), a confirmation popup shows the estimated credit cost and your remaining balance. You always approve before credits are spent
- Credits never expire. Your balance rolls forward indefinitely — unused credits stay in your account until you spend them
- Failed AI translations (due to network errors, timeouts, or server issues) do not consume credits. Credits are only charged for successful completions
- All AI features share the same credit pool — single post translation, bulk translation, string translation, content diff AI updates, and per-segment Visual Editor translation all draw from the same balance. If you have the Forge Suite Bundle, credits are also shared across all four plugins
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-ever Forge purchase, the one-time welcome pack 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 content diff refreshes. 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. Set up and use TM actively — exact matches are free, which can reduce credit usage by 20-40% on sites with repetitive content
- 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 on the Bulk Translation page before starting. If it exceeds your current balance, purchase an add-on pack in advance to avoid interruptions.
> Good to know: Translation Memory saves credits automatically. When the AI encounters a segment that has an exact match in your Translation Memory, it uses the stored translation instead of generating a new one — and no credits are deducted for that segment. The more you translate, the more credits you save over time.
[Screenshot: The Account page showing current credit balance, usage history, and the option to purchase add-on credit packs]
—