Cloud Assist feature
Cache Reuse in Cloud Assist
Smarter translation reuse. Lower repeated token usage.
Cloud Assist includes a cache reuse system designed to reduce unnecessary repeat translation work. When your site sends content for translation, REEID Translate Pro can remember previously translated strings and reuse them when the same content is translated again.
♻️
Avoid translating unchanged content again and again.
This is especially useful when you make small edits to an existing page, product, or post. Instead of translating everything from the beginning again, Cloud Assist tries to reuse what has already been translated.
The goal is not “no tokens ever.” The goal is to avoid paying again for unchanged content whenever possible.
Why this matters
AI translation cost is usually based on token usage. If a page is translated again and again from scratch, token usage can grow quickly. Cache reuse helps reduce this waste.
Example: you translate a page into Arabic, later change one sentence, and then translate again. Unchanged text can be reused, while only the changed part needs fresh translation.
This makes repeated translation work faster, more efficient, and more predictable for real websites where pages, products, and posts are often edited after publishing.
What Cloud Assist can reuse
- Gutenberg pages and posts
- Classic Editor content
- Elementor text nodes
- WooCommerce product strings
- Repeated translation runs
- Small content updates after earlier translation
- Unchanged strings inside edited pages
- Reusable translated text at smaller content level
Repeated translations should not always behave like a first-time translation.
What happens when content changes
If the source text is unchanged, Cloud Assist can reuse the cached translation. If the source text changes, only that changed text normally needs to be translated again.
Small changes may still consume some tokens because the AI still needs instructions, language context, glossary rules, and the changed text itself. This is normal.
Formatting changes and cache reuse
Some formatting changes can affect cache reuse. For example, plain text and the same text wrapped in HTML tags may be treated as different source content because the structure changed.
This is intentional and safer than blindly reusing a translation where the content structure changed.
What cache reuse does not mean
Cache reuse does not guarantee zero token usage.
Some token usage may still happen when new text is added, existing text is edited, formatting changes inside a translated string, glossary or prompt instructions change, content is split differently by the editor, or a product field is saved with changed HTML structure.
The goal is to avoid paying again for unchanged content — not to promise that every repeated translation will use no tokens at all.
Cloud Assist and privacy
Cloud Assist cache is designed for translation reuse, not for exposing user secrets. The cache stores reusable translation results for your site’s translation workflow.
Your OpenAI API key is not stored in the Redis translation cache.
Local BYOK and Cloud Assist remain separate
In Local BYOK mode, your OpenAI key stays on your WordPress site. In Cloud Assist mode, translation requests are handled through the REEID Cloud Assist service according to the selected plugin mode.
These modes are intentionally separate so users can choose the workflow that fits their site and privacy expectations.
Best practical expectation
Cache reuse works best when you:
- translate the same page or product again
- make small edits instead of rewriting the whole page
- keep glossary and prompt settings stable
- avoid unnecessary formatting-only changes inside translated strings
- retest after editing only a small part of the content
A good result looks like this:
- first translation: normal token usage
- unchanged retranslations: very low or near-zero token usage
- small edits: only changed parts consume tokens
- large rewrites: higher token usage, as expected
Why this is useful for real websites
Real websites are rarely translated only once. Product descriptions change. Landing pages are adjusted. SEO text is refined. Headings are rewritten. Small corrections happen after publishing.
Cloud Assist cache reuse is built for this reality. It helps REEID Translate Pro avoid repeating unnecessary AI translation work during editing, testing, and ongoing content maintenance.
Simple summary
Cloud Assist cache reuse helps your site translate smarter. It remembers previous translations, reuses unchanged content, and sends only changed text for fresh translation when possible.
This can reduce repeated token usage, speed up retranslations, and make multilingual site maintenance more practical.
Smarter translation maintenance for WordPress.
Use Cloud Assist cache reuse to reduce unnecessary repeated translation work when maintaining multilingual pages, products, posts, and builder content.