Keep structure where audits expect it.Translate PDFs with explicit job control.
Reduce layout drift on manuals, filings, and customer-facing PDFs. Upload from My documents, pick languages and an optional preset, then download when the async job succeeds— one credit per page, three credits included for new workspaces, Stripe when you scale.
No credit card required for your first three pages.
- 1 credit = 1 PDF pageCharged from page count at submit time
- 3 credits to startNew accounts, no card required
- Stripe checkoutCredits after successful payment
Operational snapshot
- Job states you can defend in standups: queued, running, succeeded, failed—no vague “processing” only story.
- Stack you can diagram for security reviews: Workers, D1, R2, Queues—see the Security page for wording.
- PDF-only intake so teams do not accidentally route unstructured formats through the same path.
Built for procurement questions
No vague “enterprise-grade” label—read how transport, storage, and jobs are wired, then map that to your own security packet.
HTTPS by default
Browser traffic to your deployed site and API should use TLS in production.
Cloudflare-shaped stack
Workers API, D1 for credits and job state, R2 for PDF bytes, Queues for async translation.
Clear retention story
Optional Worker cron purges (DOCUMENT_RETENTION_DAYS) plus R2 lifecycle—document what you ship; see the Data handling FAQ.
Layout fidelity
Compare structure before you sign off a release
Mock PDF chrome below is a QA teaching tool—drag the divider or use arrow keys. Real output still depends on your engine and source file.
Illustration only. DocTranslate is built for layout-heavy PDFs; fidelity varies by file and engine. Drag the line or use arrow keys when the slider is focused.
Operational proof points
PDF-first pipeline
The uploader accepts PDFs only—built for documents where structure matters.
Stripe-backed billing
Credit bundles checkout through Stripe. Your live price is whatever you set in Stripe.
Honest scope
We do not promise instant turnaround or pixel-perfect fidelity—expect production-minded output you can QA against your own checklist.
Compliance posture
Reduce release risk on layout-heavy PDFs
Localization breaks tables, footnotes, and reading order when tools treat files like plain text. DocTranslate focuses on PDF structure preservation within the limits of your engine and file—so reviewers spend less time fixing avoidable layout drift.
What to document for internal review
- Jobs:Async pipeline with explicit states (queued → running → outcome)—no fake “instant” promise.
- Billing:One credit per PDF page at submit time; Stripe Checkout for bundles—predictable unit economics.
- Evidence:Download translated PDFs from the same workspace view; retain audit notes in your own systems of record.
SOC 2 and similar attestations are not claimed here unless your deployment has them—use the security page as the technical baseline for questionnaires.
Product
Controls localization teams can explain to legal
For documents where tables, callouts, and hierarchy must survive translation—not generic “AI file” promises. Each capability below maps to something you can verify in the dashboard.
Layout fidelity first
Aims to preserve structure, tables, and reading order in translated PDFs. Outcomes still depend on your file and engine—we surface that honestly so QA can plan checkpoints.
Async jobs, explicit status
Queued → running → succeeded or failed. Track each document in the dashboard; optional realtime updates when Pusher is configured—no misleading “percent translated” theater.
Languages and controlled presets
Pick source and target languages from the supported set, plus an optional style preset (for example business default or legal / formal) so outputs stay consistent across releases.
Predictable credits
Start with three free credits, then buy bundles when volume grows. Stripe Checkout; the price your organization pays is what you configure in Stripe.
Explore by document type
Flow
Workflow
Three steps—same operational story on every screen size.
- 1
Upload your PDF
Sign in, drop a .pdf (up to 50 MB), choose source and target languages, optionally a translation preset, and enqueue the job from My documents.
- 2
Processing runs in the background
Work is handled asynchronously via your configured queue and translation service. Leave the page—status updates when you return.
- 3
Download when the job succeeds
When the job completes successfully, download the translated PDF from the same documents view. Failed runs stay visible so you can retry with context.
Pilot on your own PDFs before you standardize
Create a workspace and spend three included credits on real files—no payment step required to start.
Pricing
Predictable credits. No surprise SKUs.
Budget in pages: 1 page = 1 credit. New workspaces include 3 credits. Buy bundles when volume grows—Stripe Checkout; the amount is whatever you configure there.
3 credits free
Covers up to three pages across your first PDFs—ideal to validate layout and workflow on documents you already trust.
- Full upload → job → download flow in the dashboard
- Credits deducted by PDF page count
- Upgrade from billing when you need more
Credit bundles
Example many teams configure: ~$10 for 100 credits (100 pages)—treat that as an illustration. Your live price is in Stripe.
- Secure checkout with Stripe
- Credits added after successful payment
- Use credits for translation jobs from the dashboard
Purchasing credits requires an account; the billing page is for signed-in users.
FAQ
Straight answers
The details people ask before uploading sensitive PDFs.
What file types are supported?
PDF uploads only (.pdf). Other formats are not accepted by the uploader today.
How are credits calculated?
One credit equals one page. Page count comes from your PDF at processing time—multi-page files use multiple credits.
What do I get for free?
New accounts include three credits at signup. No credit card is required to use those first pages.
How do purchases work?
Signed-in users can buy credit bundles via Stripe Checkout. Credits are added to your balance after successful payment (webhook-backed in production).
Is translation instant?
No—jobs are asynchronous. Time depends on document size, queue load, and the translation service. Plan for background processing, not immediate downloads.
How will I know when a job finishes?
Status updates appear in your dashboard. If realtime is configured for your deployment, the UI can reflect completion without a manual refresh.
What languages and presets can I use?
The uploader offers a fixed set of source and target language codes (see the dashboard). You can also pick an optional translation style preset, such as business default or legal / formal.
How is data encrypted and where does it live?
Use HTTPS in production between browsers and your deployed site/API. PDF bytes are stored in Cloudflare R2; job state and credits live in D1. See the Security page for architecture detail you can paste into questionnaires.
Who are subprocessors for translation?
Translation is performed by an HTTP service you operate and connect to the worker (for example on Cloud Run or Modal). List that provider in your own subprocessor register—DocTranslate does not substitute for your vendor diligence.
How long are files retained?
Retention depends on your R2 lifecycle rules and deployment configuration. Document your production defaults in your privacy notice; the Security page describes the technical shape only.
Ship translated PDFs stakeholders can review with confidence
Start with three included credits, exercise the full job lifecycle in the dashboard, then add Stripe bundles when your release calendar demands more capacity.