Create your DeepL account today to access fast, accurate translations across your projects. Set up in minutes, verify your email, and connect a payment method from the dashboard.
To create your profile, visit DeepL.com, click Sign Up, enter your email and password, complete the CAPTCHA, and finalize the onboarding prompts to start translating.
Choose a plan that fits your needs. The Free tier covers basic translation tasks, Pro adds higher limits and API access, and Team enables multi-user access with centralized billing.
In your account settings, go to Subscriptions to upgrade, downgrade, or pause a plan. You can add team members, assign roles, and export invoices for accounting.
Boost translation quality with practical tools. Create glossaries for critical terms, set formality preferences, and process documents in batch to preserve layout and formatting.
Integrate with your workflow. Use the API or connect apps to automate translations, link to your CMS, and sync results with your content calendar.
Keep your usage aligned with your goals by reviewing the dashboard weekly, adjusting limits as needed, and ensuring payment details stay current to avoid any service interruption.
Create Your DeepL Pro Account: Email Verification and Onboarding
Verify the email you used for signup right away and enable two-factor authentication to lock the account before you translate.
Set a strong password, then open the DeepL Pro dashboard, go to Security, and scan a QR code with an authenticator app. Save recovery codes in a secure manager.
Email Verification Steps
1) Use a real email on the signup page and submit the form.
2) Open the inbox for a message from DeepL; click the verification link or paste the code into the prompt.
3) If the email does not appear, check spam or filters; add [email protected] to the allowlist and request a new message from the same page.
4) Return to the dashboard and confirm the status shows as Verified.
| Step | Action | Erwartetes Ergebnis |
|---|---|---|
| 1 | Sign up with a valid email | Verification email is sent |
| 2 | Click the link or enter the code | Email is verified |
| 3 | Enable 2FA in Security | 2FA is active |
| 4 | Provide billing method and set roles | Account ready for Pro use |
Onboarding Configuration
Configure billing, API access, and team permissions. In Billing, choose a plan that matches expected usage and set up alerts to notify you about charges or limits.
In Team settings, invite colleagues and assign roles (Viewer, Editor, Admin) to control access. For API users, generate keys, store them securely, and rotate any unused keys on a regular schedule.
Choose a Plan: Free vs Pro and Team Options
Go with the Free plan if you translate modestly each month and do not need automation. Pro adds API access and higher quotas for developers and power users. Team brings multi-user collaboration with centralized management. Pick the path that fits your workflow and scale when needed.
- Free Plan: Access through the web app, all supported languages, no API access, a monthly translation quota, standard support, and translation history stored in your account for quick reference.
- Pro Plan: API access for automation and integrations, higher translation quotas, glossary features to ensure terminology consistency, priority support, and access to advanced translation tools.
- Team Plan: Multi-seat access with centralized billing, admin controls to add or remove members, usage analytics, a shared terminology glossary, and collaborative workspaces for teams.
How to choose quickly:
- Estimate monthly translation volume and whether you need automated workflows or app integration.
- Determine if collaboration with teammates is essential.
- Match your budget to the plan level, noting that you can switch plans anytime from the Billing page.
Configure Billing: Payment Methods, Invoices, and Billing Cycles
Set up annual billing with a primary card to lock in savings and keep renewals simple.
Payment Methods
Link a Visa, MasterCard, or American Express for instant charges and reliable processing. If you prefer flexible checkout, add PayPal to your account for quick payments and easy refunds where supported. For corporate accounts, request wire transfers as a manual option; transfers can take 2-3 business days and require a reference number. Your account supports USD, EUR, and GBP by default, with other currencies available by request. Enable auto-renewals to keep services active without interruption.
Invoices and Billing Cycles
Invoices appear as PDFs in the Billing Center and are emailed automatically after each payment. Each invoice shows the service period, itemized charges, tax details, and your billing address. If you operate in a VAT region, provide your VAT ID to receive tax treatment on eligible invoices. Choose a cycle that matches cash flow: monthly for predictable expenses or annual to reduce total cost. You can switch cycles anytime from the Billing page; changes take effect at the next renewal. Upgrading or downgrading mid-cycle prorates the charge for the current period. Enable renewal reminders a few days before due dates, and export spend data as CSV for accounting and audits.
Manage Subscriptions: Upgrades, Downgrades, Pauses, and Renewal Rules
Upgrade when your translation needs exceed your current limit; upgrades activate immediately and the prorated difference is billed on your next invoice.
Upgrades and Downgrades
- Upgrades: Immediate access to higher quotas and API credits; you pay the prorated difference on your next billing date; the new tier applies instantly, so you can continue work without interruption.
- Downgrades: Take effect at the end of your current billing period; you retain your current features until renewal, then revert to the lower tier; after the switch, quotas and API limits are aligned with the new plan.
- How to change: In your account, go to Subscriptions, click Change Plan, select the desired tier, and confirm. The system applies rules above automatically.
- Tips: Review usage before upgrading or downgrading; set reminders a few days before renewal to adjust the plan if needed.
Pauses and Renewal Rules
- Pauses: You can suspend service for up to 90 days per cycle; during a pause you won't be billed and translations queued stop accumulating; once resumed, the renewal date remains the same and billing resumes accordingly.
- Renewal rules: Auto-renew is enabled by default; you can disable auto-renew or pause to halt charges. Renewal date is fixed per cycle (monthly or yearly); mid-cycle upgrades are billed pro rata, mid-cycle downgrades take effect next cycle. Refunds follow policy; contact support for eligibility within the allowed window.
- How to pause or adjust: Use the Pause option in Subscriptions for the desired duration; after pausing, you can resume from the same screen and your renewal date will stay aligned.
Create and Apply Glossaries to Steer Translations
Create a dedicated glossary for your project and apply it to all DeepL translations to keep terminology consistent across languages.
Get your API key from the DeepL Pro dashboard, create a dedicated automation account, and run a 500–1,000 character test to verify formatting and error handling before scaling. Make a plain POST call to https://api.deepl.com/v2/translate with parameters: auth_key, text, and Translation not available or invalid.. Optionally include source_lang, formality and preserve_formatting to keep HTML or Markdown in the result. For larger units, segment text into chunks under 1,000–2,000 characters and translate sequentially to preserve context. For document translations, use /v2/document to upload a file and receive the translated file or a download link. Use a callback URL if your workflow requires automatic delivery to storage, a ticketing system, or a content repository. Check the response structure to extract the translated file and any status codes you need to handle. Monitor usage with alerts, and create a retry plan for 429 responses. If a call fails due to rate limits, back off for a brief period (e.g., 30–60 seconds) and retry up to 3 times per job. Keep a log of translations for auditing and reconciliation with your original text. Security matters: store the API key in environment variables or a secrets manager, rotate keys on a schedule, restrict access to the automation host, and enable IP allowlisting if your plan supports it. Use separate keys per workspace to isolate projects and simplify debugging. In your automation layer, use an HTTP action to issue a POST to /v2/translate or /v2/document. Pass text or a file and capture the translations field from the JSON response (translations[0].text or translations[0].text for documents). Map the translated text to your target field, and store metadata such as source_lang, target_lang, and timestamp alongside the result. If you translate documents, verify file integrity after download and preserve original file naming for traceability. Translate customer inquiries received by email or chat and push replies to your agent, with the translated content preceding the native language. Sync language pairs in a translation table within a spreadsheet to drive multilingual workflows. Connect to a CRM to auto-update notes with translated summaries, or post translations to team channels in Slack or Teams. For content pipelines, translate product descriptions and docs, then approve within a content system, maintaining a version history of source and translated text. Begin every project by recording the audience, domain terms, and tone in a one-page brief, then translate against that brief to minimize drift. Create a glossary of 100 core terms and phrases aligned with your brand and update it after each release, aiming for glossary term matches to appear in at least 75% of first-pass segments. Context matters: identify target audience, document field-specific terms, and flag phrases requiring localization. Use a quick checklist: audience type, content goal, required units (dates, numbers, currencies), and regional constraints. Use translation memory (TM) to capture long-tail terms and ensure consistency across modules; aim for a TM match rate of ≥ 60% on non-glossary terms in your initial pass. Formatting rules: preserve placeholders, maintain headings and lists, and align formatting with the target platform. Localize dates, numbers, and measurement units; keep date formats like DD/MM/YYYY or MM/DD/YYYY as required; ensure currency symbols appear after the amount when the locale dictates (for example, 1,000 € vs €1,000). For UI copy, limit phrases to 2-6 lines per screen and 8-12 words per line to reduce wrapping issues. Consistency ensures reliable results: use TM and glossary for every file, run a term-check pass, and perform a cross-file QA to identify drift. Track metrics such as glossary-term coverage, TM reuse rate, and post-edit rate, and aim for over 75% coverage and under 3% term drift after human review. Tag any new terms in the glossary within 24 hours to keep teams aligned. Workflow tips: start with automatic checks, then a human review focused on accuracy of terms, tone alignment, and formatting fidelity. Use a two-stage QA: a linguistic check for translation adequacy and a layout check for placeholder integrity; fix issues in the next build and re-check. Allocate 20 minutes per 1,000 words for review in standard projects; for tight timelines, cap first-pass fix time at 10 minutes per 500 words. Pitfalls to watch for: inconsistent term usage, placeholder drift, date and number mismatches, and misinterpreting abbreviations. Use a 3-step check: glossary lookup, numeric consistency, and layout verification with a sample screenshot.Use the DeepL API and Integrations for Automation
REST calls and data flow
Popular automation patterns
Quality-Driven Translation Tips: Context, Formatting, and Consistency
