Script fit
Perso-Arabic (Nastaliq)
right-to-left · abjad- Primary script only
Language coverage
Dari is the Afghan variety of Persian, written in Nastaliq-style Perso-Arabic script with right-to-left composition and vocabulary that diverges substantially from Iranian Farsi.
Translating Dari accurately requires linguists who understand the script, the specific Afghan lexicon, regional dialect boundaries between Kabuli, Herati, and Mazari forms, and the cultural context of content produced for Afghan audiences. MoniSa's Dari linguists are verified native speakers, matched to the regional variety your content needs.
Medical interpretation deployment is adjacent proof for similar work, useful for judging the review model, not a one-to-one language promise.
Perso-Arabic (Nastaliq) RTL
Translation fit
Dari scope checkActive coverage is reviewed against audience, script, dialect, content type, and proof need before work is planned.
Language readiness
Script direction, dialect scope, service coverage, and proof context are checked before timing or reviewer assumptions get locked too early.
Coverage model
Dari is the Afghan variety of Persian, written in Nastaliq-style Perso-Arabic script with right-to-left composition and vocabulary that diverges substantially from Iranian Farsi. Translating Dari accurately requires linguists who understand the script, the specific Afghan lexicon, regional dialect boundaries between Kabuli, Herati, and Mazari forms, and the cultural context of content produced for Afghan audiences. MoniSa's Dari linguists are verified native speakers, matched to the regional variety your content needs.
Request a Dari Translation Quote
| Service line | Planning status | Dialect scope | Start path | Turnaround note |
|---|---|---|---|---|
| Translation and review | Active coverage | Kabuli, Herati, Mazari | Brief review | Confirmed on brief |
| AI data annotation | Active coverage | Standard | Brief review | Confirmed on brief |
| Audio transcription | Active coverage | Kabuli, Herati | Brief review | Confirmed on brief |
| Subtitling | Active coverage | Standard | Brief review | Confirmed on brief |
| Dubbing | Active coverage | Kabuli | Brief review | Confirmed on brief |
Service fit, reviewer continuity, and turnaround are confirmed against the live brief before production begins.
Buyer need
For Dari, the buyer risk is variant lock, RTL handling, and terminology neutrality, not generic translation quality. MoniSa confirms script, dialect, reviewer, and service fit against the brief before production begins.
Service answer
Dari belongs to the Western Iranian branch of the Indo-Iranian language family and is one of two official languages of Afghanistan alongside Pashto. Between 25% and 50% of Afghanistan's population speaks Dari natively, with the language functioning as the country's primary lingua franca across ethnic boundaries. The Nastaliq Perso-Arabic script uses 32 letters and reads right-to-left. While Dari shares mutual intelligibility with Iranian Farsi, its vocabulary diverges in government, military, and everyday terminology. Machine translation engines trained primarily on Iranian Farsi corpora routinely substitute Iranian vocabulary into Dari output, producing text that reads as foreign to Afghan audiences.
MoniSa confirms the reviewer path, review depth, and delivery timing for Dari in the project brief. Every assigned linguist is verified for the variety and domain your project needs. We publish coverage and review depth, not the routes we recruit through.
A humanitarian or health program targeting Afghan populations
requires Dari materials and existing vendors cannot differentiate Dari from Iranian Farsi in vocabulary, register, or orthographic conventions.
A security-sensitive project
needs Dari translation with security-scoped handling and dialect-matched linguists for Kabuli, Herati, or Mazari content.
An AI or NLP team building Afghan-language datasets
discovers that training data labeled "Persian" contains almost no Dari-specific vocabulary, creating downstream model failures for Afghan contexts.
A multilingual program includes Dari alongside Pashto
and the vendor pool treats both as interchangeable afterthoughts rather than distinct languages with separate linguist requirements.
Dari translation workflow
All Dari work follows MoniSa's 3-layer review model: translator (domain-matched, verified for Afghan Dari versus Iranian Farsi distinction), editor (bilingual accuracy and terminology adherence with Farsi-interference screening), proofreader or community validator (cultural and contextual review for Afghan audience appropriateness). Review depth is scoped to the language pair, task type, and buyer risk.
Dialect, domain, and volume mapped before assignment. For Dari, scoping includes confirming whether the target audience is Kabuli, Herati, or Mazari, using the wrong dialect register for Afghan government content versus diaspora-facing material produces noticeable errors.
Dari translation follows the standard TEP workflow with an added check for Farsi interference. Editors verify that Iranian Persian vocabulary and constructions have not bled into the Afghan Dari output, a common failure mode when linguists work across both varieties.
Batch delivery with QA reports covering terminology adherence, dialect consistency, and RTL rendering validation. For conflict-zone content, delivery uses encrypted channels with source material compartmentalization.
Backup path
Turnaround is confirmed in the project brief. For specialized domains, backup linguists are identified at scoping.
Reviewer path
Quality metrics are identical for rare and high-resource languages. Review layers are not reduced based on linguist scarcity.
Sourcing status after scope
Sourcing path and review depth are confirmed in the project brief.
Live interpreting
Dari reaches MoniSa more often as a spoken request than a written one — a hearing, an appointment, a call that cannot continue until someone present speaks Dari. That work is scoped separately from translation on this page, because it is bought in a different unit.
Interpreting in Dari means a qualified interpreter renders a live conversation between Dari and another language, delivered in one of three ways: on an audio call, over a video link, or in the room. It is not translation. Translation produces a written deliverable and is quoted on volume, file type and review depth; interpreting is a live event with a date, a duration and a setting, and is booked as time. That is also how the two appear on a quote, with content on one line and time on the other, so a matter that needs both is scoped as two pieces of work rather than one. MoniSa sources and screens interpreters across 300+ languages and 4,500+ dialects from its network of 110,000+ verified language specialists, and operates under ISO 9001 and ISO 27001 certification.
Screening for a Dari session starts with the variety the speaker actually uses, because a near match is not a match once a conversation is under way. The interpreter is then checked in the working pair and screened against the setting the session comes from, so a clinical encounter, a legal proceeding and a school meeting count as separate qualifications rather than one. Everyone assigned signs the confidentiality agreement before receiving access, and named backup coverage is recorded alongside the primary assignment. What MoniSa publishes is the coverage and the screening, never the routes it recruits through.
Audio line
An audio line connects faster than any other modality, which makes it the right route for short, unscheduled exchanges such as an intake call, a benefits query, or an appointment booking, where nothing visual carries meaning.
Over-the-phone interpretationVideo link
A live video link is used when a document, a device, a physical examination or a signed language is part of the conversation, and when the people in the room and the interpreter need to see each other without anyone travelling.
Video remote interpretingClinical setting
A clinical encounter adds a credential requirement and a domain screen on top of the language check, because a summarised symptom or a softened instruction changes the care that follows.
Medical interpreter servicesRelated proof
Medical interpretation deployment is adjacent proof for similar work, useful for judging the review model, not a one-to-one language promise.
Related case study
Healthcare communication controls and conflict-sensitive reviewer routing.
Buyer questions
The questions buyers send before a scope conversation, answered on the page rather than in a meeting. Take them to your team, then send us the one we did not answer.
Yes. MoniSa's Dari linguists are verified native speakers, with reviewer fit confirmed before assignment. Turnaround is confirmed in the project brief. The sourcing path is confirmed in the project brief.
Dari and Iranian Farsi share a script and broad grammatical structure but diverge in vocabulary, pronunciation, and formal register. MoniSa assigns only Afghan-origin linguists to Dari work and editors screen specifically for Iranian Farsi vocabulary interference, a common failure mode when vendors treat the two as interchangeable.
Timing is confirmed after project brief. Buyers get the likely sourcing path, service fit, and related proof rather than a delivery promise.
Project-scoped quality data stays inside the linked case study. On live work, review depth, reporting, and acceptance logic are confirmed in scope before production starts.
Translation is written: a document, a record, a subtitle track, delivered as content and quoted on volume and review depth. Interpreting is spoken: a live conversation on the phone, over video or in the room, booked as time with a date attached. A hearing, an appointment or a call needs an interpreter; a form, a notice or a record needs a translation, and most matters need both. MoniSa scopes them separately, because the sourcing, the screening and the unit of work differ, and confirms which one the brief actually needs before quoting.
You are told before a date is agreed, not after. Coverage is reported pair by pair as staffed today or needing a recruitment window, with the window stated — in writing, while the scope is still being agreed. Nobody new goes onto live work until a pilot batch has been reviewed and signed off. A coverage claim you cannot check before signing is not coverage.
Next step
A useful brief names the language, content, deadline, review depth, and proof the buying team needs.
Production-ready brief
01Language pair, dialect, and script02Content or data type03Volume and deadline04QA and reviewer requirement05Security and access requirement06Proof needed for buyer approval