Uzbek records may use modern Latin, Uzbek Cyrillic, historical Arabic script, Russian text, handwriting, or bilingual fields. A country, name, emblem, or alphabet does not prove that every page is Uzbek.
Use checkout for an eligible ordinary typed file. Choose Other, then enter Uzbek in other_source_language.
Request a quote for uncertain or mixed language, Latin and Cyrillic or Arabic-script conflicts, older records, handwriting, damaged scans, dense layouts, unclear page count, name discrepancies, or recipient-specific work. The quote form names Uzbek in both selectors. Review USCIS translation guidance, the language directory, or birth certificate translation details.
Common Uzbek records reviewed
Tug‘ilganlik haqida guvohnoma— birth certificateNikoh tuzilganligi haqidagi guvohnoma— marriage certificateNikohdan ajralganlik haqidagi guvohnoma— divorce certificateID-karta— identity cardSudlanmaganlik (yoki sudlanganlik) to‘g‘risida ma’lumotnoma— police certificateAkademik ma’lumotnoma (transkript)— academic transcript
These native-first labels are examples, not a claim that every historical or regional record uses the same title.
Uzbek documents we translate
Tug‘ilganlik haqida guvohnoma — Birth certificate
Nikoh tuzilganligi haqidagi guvohnoma — Marriage certificate
Nikohdan ajralganlik haqidagi guvohnoma — Divorce certificate
ID-karta — Identity card
Sudlanmaganlik (yoki sudlanganlik) to‘g‘risida ma’lumotnoma — Police certificate
Akademik ma’lumotnoma (transkript) — Academic transcript
Is the source actually Uzbek or only from Uzbekistan?
Readable vocabulary, headings, field labels, issuer text, seals, and every supplied page establish whether each passage is Uzbek.
Uzbekistan issues civil records in Uzbek or Russian, and some current records are bilingual. An Uzbek surname, place, national emblem, citizenship, ethnicity, or Latin, Cyrillic, or Arabic script does not identify the language of a full packet.
Review separates Uzbek from Russian, Karakalpak, Tajik, Kazakh, Kyrgyz, Turkmen, and Uyghur. Each language remains tied to its printed field. A parallel column is not used to rebuild unclear text in another.
Every page, attachment, and reverse side must be supplied before scope is confirmed. Mixed wording, cropped headings, unclear issuer text, or uncertain language requires quote review. Certified translation reports the readable source; it does not infer language, identity, authenticity, or completeness from country or script.
How is modern Latin-script Uzbek preserved?
Modern Latin Uzbek is checked character by character, including O‘, G‘, tutuq marks, Sh, Ch, and Ng exactly where printed.
The source controls capitalization, spacing, punctuation, digraphs, and apostrophe-like marks in names, headings, dates, and identifiers. O‘/o‘ is not flattened to O/o, and G‘/g‘ is not flattened to G/g. Sh/sh, Ch/ch, and Ng/ng remain tied to the visible spelling.
Curly apostrophes, straight apostrophes, and modifier-letter forms are not treated as interchangeable when the image distinguishes them. A familiar modern spelling does not authorize silent correction of an older or inconsistent printed form.
OCR may drop the mark after O or G, split a digraph, or substitute a keyboard apostrophe. Extracted text is supporting evidence only. Faint type, damaged characters, conflicting repetitions, or a requested identity spelling requires a clearer image or quote review rather than normalization from memory.
How are Uzbek Cyrillic and Soviet-era records controlled?
Uzbek Cyrillic remains source-bound, including Ғ, Қ, Ў, and Ҳ, and is never treated as Russian solely because it uses Cyrillic.
The Uzbek Cyrillic letters Ғ/ғ, Қ/қ, Ў/ў, and Ҳ/ҳ must not be flattened into visually similar Russian or basic Cyrillic forms. Readable vocabulary and field context identify language; the alphabet alone does not.
Soviet-era civil, school, military, court, and residence records may contain Uzbek Cyrillic, Russian, amendments, or bilingual columns. Review follows the issuer, date, title, fields, names, numbers, seals, notes, and reverse side. Parallel columns are not assumed to match word for word.
An older spelling is not silently modernized into Latin Uzbek. If transliteration is required, the chosen form stays traceable to the image, linked identity evidence, and recipient instructions. Mixed scripts, damaged type, disputed letters, or unclear transliteration rules require quote review.
How are historical and Afghanistan Arabic-script Uzbek handled?
Arabic-script Uzbek is reviewed right to left against the image, with joining, letters, visible vowels, punctuation, and embedded numbers preserved.
The Library of Congress table distinguishes Uzbek Arabic-script conventions used in the 1920s from contemporary Afghanistan usage, including different vowel treatment. That table is a cataloging reference, not a universal passport, identity, pronunciation, or recipient standard.
Review preserves character identity, order, joining, visible vowel marks, punctuation, dates, and embedded left-to-right numbers. Modern Latin wording is not substituted, and omitted vowels are not supplied.
Arabic script alone does not prove the text is Uzbek. Persian, Dari, Uyghur, and other languages require separate identification from readable wording. Broken joining, reversed OCR, mixed direction, faint marks, historical typography, or unclear language requires a usable image and quote review rather than an automatic conversion.
Which Uzbekistan civil and identity records need document-specific review?
Each civil or identity record is scoped by its printed title, issuer, language, fields, registration data, seals, dates, and reverse side.
Records may include birth, death, marriage, divorce, adoption, name-change, ID-card, passport, police, court, or school documents. Current U.S. reciprocity guidance describes Uzbek or Russian civil booklets, QR codes, wet seals, duplicates, and older valid formats. Current ID cards may use Uzbek Latin and English.
Those details are format clues, not proof that a supplied record is genuine, complete, written in one language, or sufficient for a recipient. Review follows the actual FHDY or FXDYO wording when printed, issuer, record type, names, dates, places, registration number, amendments, QR text, seals, signatures, attachments, and page backs.
Blank or unreadable fields are not completed from a familiar layout. Missing backs, damaged marks, mixed-language attachments, or conflicting record forms require a clearer file or quote review.
How are names, patronymics, name changes, and machine-readable data controlled?
Every printed name form stays tied to its field, order, ending, spacing, punctuation, script, identifier, and source position.
Review preserves each surname, given name, patronymic, former surname, initial, spacing, apostrophe, and Latin, Cyrillic, or English form. A patronymic is not invented, initials are not expanded, and Cyrillic is not silently normalized to Latin.
Passports, ID cards, civil records, machine-readable lines, QR text, and customer spellings may be compared only when supplied and linked to the same person. A linked spelling can guide recipient-sensitive rendering, but it does not erase a different printed source form.
Differences do not prove error, kinship, identity, nationality, ethnicity, gender, or a legally preferred spelling. Changed surnames, inconsistent endings, disputed apostrophe forms, or unclear recipient rules require quote review. The translation keeps every source-supported form traceable without declaring one spelling correct for every agency or system.
How are QR codes, seals, scans, numbers, and page order checked?
Every page and reverse side is checked for QR codes, seals, signatures, photographs, numbers, dates, notes, tables, margins, and sequence.
Review follows the image and page order. It covers registration numbers, dates, a 14-digit personal number where printed, machine-readable lines, amendments, handwriting, wet seals, photographs, identifiers, and bilingual field positions. A QR code is visible source content; translation does not verify a registry or authenticate its data.
OCR may lose Uzbek apostrophe marks, confuse Uzbek and Russian Cyrillic, reverse Arabic text, split identifiers, or merge neighboring bilingual columns. Extraction never replaces direct image review.
Blur, glare, compression, bleed-through, cropped margins, damage, handwriting, missing backs, or inconsistent page numbers requires a clearer file or quote review. Unreadable content is identified instead of reconstructed from a nearby field, familiar form, or likely phrase.
What does the receiving organization require?
Recipient rules control the submission packet; checkout fits eligible typed Uzbek files, while complex or recipient-sensitive work needs a quote.
For USCIS, 8 CFR 103.2(b)(3) requires a full English translation plus certification of completeness, accuracy, and translator competence. Follow current recipient instructions. A faithful certified translation is separate from a filing decision.
Use Start your order for an eligible clear, complete, ordinary modern typed file by choosing Other and specifying Uzbek. Use Get a quote with named Uzbek for mixed or uncertain language, script conflicts, older records, handwriting, damage, dense layouts, unclear page count, name discrepancies, or recipient-specific work.
Corpus provides certified written-document translation, not notarization, apostille, mailing, interpretation, retrieval, registry verification, evaluation, or legal advice. It does not guarantee acceptance, authenticity, identity, equivalency, legal effect, or immigration outcomes.
FAQs
What does certified Uzbek document translation cost?
Eligible clear, complete, ordinary modern typed Uzbek files start at $19.99 per page after scope confirmation. Mixed, handwritten, historical, dense, damaged, uncertain, or recipient-specific files need quote review.
How do you confirm that a document is written in Uzbek?
Readable vocabulary, script, headings, field labels, issuer text, seals, and every page are reviewed. Uzbekistan as the issuing country, an Uzbek name, or Latin or Cyrillic script alone does not prove the whole packet is Uzbek.
How are Latin-script Uzbek letters and apostrophes handled?
The printed O‘, G‘, tutuq marks, Sh, Ch, Ng, capitalization, spaces, and punctuation are checked against the image. Apostrophe-like characters are not silently treated as identical when the source distinguishes them.
How are Uzbek Cyrillic and Arabic-script records handled?
Uzbek Cyrillic letters and right-to-left Arabic-script forms are preserved from the source. Older, mixed, or uncertain-script files need review rather than automatic conversion to modern Latin spelling.
Which Uzbek documents can be reviewed?
Birth, death, marriage, divorce, adoption, name-change, identity, passport, police, court, education, employment, medical, military, and other written records can be reviewed when supplied. The actual language, issuer, fields, condition, and recipient instructions control scope.
How are names, QR codes, seals, and bilingual fields checked?
Every printed name form, patronymic, identifier, QR code, seal, signature, date, number, parallel field, reverse side, and page position is checked without inventing corrections, identity matches, or authenticity.
When does standard 24-hour delivery apply?
Standard 24-hour delivery applies after scope confirmation only to eligible clear, complete, ordinary modern typed Uzbek files with known language, script, page count, condition, name treatment, and recipient scope.
Should I start an order or request a quote?
Start an eligible file by choosing Other and specifying Uzbek. Request a quote for uncertain or mixed language, Latin and Cyrillic or Arabic-script conflicts, older records, handwriting, damage, dense layouts, unclear page count, name discrepancies, or recipient-specific work.