Frequently Asked Questions
Quality
How is this different from Google Translate?
Google Translate processes sentences in isolation. PageTurner analyzes your entire documentation first — extracting technical terminology, building a consistency dictionary, and understanding domain context — then translates with that context enforced across every page.
The result: "repository" translates to the same word on page 1 and page 200. Generic tools average 65–70/100 for technical content. PageTurner averages 91/100.
What quality can I expect?
Based on 19 production deployments:
| Metric | Score |
|---|---|
| Term Consistency | 99%+ |
| Technical Accuracy | 94% |
| Structure Preservation | 100% |
| Overall Quality | 91/100 |
Major languages (Spanish, French, German, Japanese, Chinese, Korean) score 91+/100. Less common languages score 85–90/100.
Can I see the quality before committing?
Yes. For commercial projects, we translate a sample of your documentation first — free, no commitment. For open source, browse any of our 19 live demos to see actual output.
Will my React components and code blocks break?
No. PageTurner preserves all JSX/MDX component structure, code blocks, inline code, import statements, and links. Only human-readable text content gets translated.
If something does break, contact us — it's a bug and we'll fix it.
Pricing
How much does it cost?
Open source (Founding Partner Program): Free for select high-profile projects. Apply here.
Commercial: Custom pricing based on documentation size, number of languages, and update frequency. Updates cost significantly less than initial translation thanks to translation memory.
See pricing or contact us for a quote.
How long does translation take?
Typical times:
| Documentation Size | Languages | Time |
|---|---|---|
| 50 pages | 3 | 10–15 minutes |
| 100 pages | 3 | 20–30 minutes |
| 200 pages | 3 | 40–60 minutes |
Updates with translation memory: 2–5 minutes for typical changes.
Framework Support
What frameworks are supported?
Currently we support Docusaurus documentation sites with full MDX and React component preservation.
Support for additional frameworks is planned. Contact us if you use a different framework — we'd like to understand your needs.
Security
Is my source code safe?
Yes.
- Your code is processed via secure APIs (GitHub, LLM providers) over HTTPS/TLS
- No source code is stored on PageTurner servers
- You control GitHub permissions — read-only access is sufficient
- Translations are created in repositories you own
- LLM providers do not use your content for model training (per their enterprise agreements)
Updates & Maintenance
How do updates work?
When your source documentation changes, PageTurner's CI/CD pipeline automatically:
- Detects which pages were modified
- Retranslates only the changed content
- Redeploys the updated site
You don't need to trigger anything. Updates typically cost 60–80% less than the initial translation.
Can I customize or correct translations?
Yes. You can edit translated files directly in the GitHub repository. Translation memory preserves your edits — future automatic updates won't overwrite your corrections.
You can also provide a terminology list upfront (e.g., terms that should stay untranslated or have specific translations).
About the Demos
How were the demo translations created?
We translated 19 production-quality documentation sites across 13+ languages to demonstrate the pipeline. Each demo was built from the project's public repository using our full translation engine — the same process we use for partners. Browse the demos.
Can I use PageTurner for my project?
Yes. We're onboarding founding partners (free for qualifying OSS projects) and commercial beta customers. Get started.
Get Help
- Contact us — We respond within 24–48 hours
- Email: hello@page-turner.com
- Beta Program — Program details and application