Everything you need
to get translating.

Verto is a multi-tenant workspace, which means the moment you sign up, a brand-new isolated workspace is created just for you. Nothing you upload is ever visible to another customer.

Step-by-step

1. Sign up at /login with your email and a password. A fresh workspace is minted on the spot — no team setup needed for solo users.
2. Verify your email. We send a verification link to your inbox; click it to activate your account. You can browse Verto unverified, but file uploads and a few other actions are gated until verification.
3. Open the dashboard. First-load shows your daily word goal (defaults to 500 words), a recent-projects list (empty until you create one), and your global TM and glossary stats.
4. Create a project. Hit "New project" on the Projects page, pick source and target languages, and optionally set a deadline.
5. Upload a file. Drop a DOCX, PPTX, XLSX, PDF, XLIFF, or any of the supported formats. Verto parses it into translatable segments while preserving formatting tags.
6. Start translating. Click the file to open the editor. Type into the target column, hit Ctrl+Enter to confirm and move to the next segment.
7. Export. When you're done, export the file back in its original format with your translations baked in.

The editor is a bilingual grid: source on the left, your translation on the right, one row per segment. Tags from the original document appear as non-editable pills you can re-insert wherever they belong in the target.

Keyboard shortcuts

Tag handling

Inline formatting (bold, italic, hyperlinks, footnotes, etc.) is preserved as numbered pills like ⟨T1⟩…⟨/T1⟩. You re-insert them in the right spots in your translation — the editor warns you if any are missing or out of order before you confirm.

Right-side panels

• Translation memory. Live matches from your TM as you move between segments, with similarity percentages.
• Glossary. Approved terms found in the source, with their canonical target translation.
• Machine translation. Side-by-side suggestions from any MT providers you've configured.
• AI chat. A focused chat with the segment's source, target, and language pair as context — useful for "is this ambiguous?", "give me three alternative phrasings", or terminology questions. Team plan

Built-in QA checks

Verto runs eleven QA rules over confirmed segments and flags issues inline. They cover:

• Missing or extra tags vs. the source
• Empty targets and untranslated (source-equals-target) segments
• Number mismatches between source and target
• Forbidden terms (terms your glossary marks as "do not use")
• Arabic-specific checks — Western "?" instead of "؟", mixed Arabic/Western numerals, and Kashida overuse

Verto's TMs and glossaries import directly from the formats you already have, so you don't have to start from zero when you migrate from Trados, memoQ, or Phrase.

Supported import formats

What the import does

• Parses the file and shows a preview so you can map columns to fields.
• De-duplicates on a hash of the source text — re-uploading the same TM won't double-count entries.
• Existing entries are upserted (target text is updated if the source already exists), not overwritten blindly.

Exporting

Any Verto TM can be exported back to TMX 1.4 from the TM page. Glossaries can be exported as Excel or CSV. Your data is yours — leaving Verto is a one-click operation.

Verto parses the following file types into translatable segments and re-bakes your translations into the original format on export:

PDF handling

PDFs are processed with two layers. Digital PDFs are parsed directly with pdfplumber for clean text extraction. Scanned pages — and pages where the embedded text is garbled (a common problem with right-to-left PDFs) — automatically fall back to Claude Vision OCR to read the page as an image.

Images embedded in PowerPoint and Word

PPTX and DOCX filters can also run vision OCR on embedded images, so text inside diagrams, screenshots, and infographics is extracted into translatable segments alongside the regular body text.

Verto was built with Arabic in mind from day one. RTL handling isn't a checkbox bolted on afterwards — it touches the editor, the file filters, the QA layer, and the export pipeline.

Detected RTL languages

The following are treated as RTL throughout Verto: Arabic (ar), Hebrew (he), Persian / Farsi (fa), Urdu (ur), and Yiddish (yi).

What Verto does for you on export

• Word (.docx): applies <w:bidi/> to translated paragraphs so reading direction flips automatically when the file opens.
• Excel (.xlsx): sets rightToLeft="1" on the sheet so columns read right-to-left.
• PowerPoint (.pptx): mirrors slide layouts by swapping shape X-positions so the layout reads naturally in Arabic — but preserves table column order, because mirroring tables truncates content.

Arabic-specific QA

The QA engine ships rules built specifically for Arabic translators:

• Western ? used instead of the Arabic question mark ؟
• Mixed numeral systems — Arabic-Indic ٠١٢ vs Western 012 in the same target
• Kashida (ـ) overuse, which is a common artifact of pasted text

Solo users can use Verto without ever inviting anyone. Once you're working with translators or reviewers, the Team plan unlocks the collaboration layer.

Team-only features

• Multiple users in one workspace (up to 10 on Team, unlimited on Custom)
• Project assignments — assign specific files to specific translators or reviewers
• Document splitting — divide a file into contiguous chunks by segment count, word count, or character count, and assign each chunk to a different translator
• Shared TMs & glossaries across the whole workspace
• Comments & reviews threaded on individual segments
• AI chat in the editor

How assignment works

1. The project manager opens a project and clicks "Assign translators".
2. They pick which workspace member translates and which reviews each file.
3. Verto sends the assignee an email notification so they don't need to check the dashboard.
4. The assignee opens the file and translates only the part assigned to them.

Splitting a long file

For deadline-driven jobs, you can split a file into ranges. Pick the unit (segments, words, or characters) and the number of parts, and Verto computes balanced ranges. Each split is assigned independently and can be reconsolidated later from the toolbar.

Verto integrates with ten machine-translation and LLM providers. You can mix-and-match: use DeepL for European languages, Claude for nuanced rephrasing, GPT for the AI chat panel — whatever suits your work.

Supported providers

Bring your own keys (BYOK)

Add your own API keys in Settings → Machine translation. When a workspace key is set, it overrides any system default for that provider — meaning your usage hits your billing relationship with the provider, not ours.

AI chat in the editor

On the Team plan and above, the editor has a dedicated AI chat sidebar. Every message you send carries the active segment's source, target, and language pair as context, so you can ask things like "what's the natural Arabic equivalent of this idiom?" without having to paste anything.

Verto runs on four plans. The full live comparison is on the pricing page — the table below is the at-a-glance version for the limits people ask about most often.

Trials

Pro and Team both offer a 30-day free trial. You enter card details at checkout, but you're not charged until the trial ends, and you can cancel anytime during the trial with no charge.

How payments are processed

Billing runs through Lemon Squeezy, our merchant of record. They handle taxes (VAT, sales tax, GST), invoicing, and dispute resolution. Cards, Apple Pay, and Google Pay are all supported at checkout.

Cancelling and downgrading

• Cancel anytime from Settings → Billing → Manage subscription — that opens the Lemon Squeezy customer portal where you can cancel, switch interval (monthly ↔ yearly), or update payment details.
• When you cancel, your plan stays active until the end of the period you've already paid for.
• Downgrading doesn't delete your data. If you have more projects or users than the lower plan allows, existing ones keep working — you just can't create new ones above the new limit until you upgrade again.