A certificate arrives with a round seal over a signature, a rectangular registration stamp, and a small handwritten date. Translating only the typed paragraphs can leave out details that help identify who issued the document and what happened to it.
The hard part isn’t just reading the stamp. You also have to decide whether to translate its words, describe its appearance, reproduce it as an image, or use more than one method. The receiving organization may have its own rules, and a translation convention that works in one country may not fit another.
This guide is for translation teams handling official documents. It separates marks on the source document from a translator’s own certification, explains the available options, and gives you a practical review process. The goal is to make each visible mark traceable without inventing text or promising that one presentation will suit every recipient.
What should you do with stamps and seals?¶
Treat a stamp or seal as part of the source document, then decide how to represent it based on its content, readability, and the recipient’s instructions. A seal can identify an issuing authority, record registration, show that a fee was paid, or confirm that a copy was made. Sometimes its wording matters; sometimes the fact that a seal appears is the relevant information.
The New Zealand Society of Translators and Interpreters (NZSTI) guideline says fee stamps, official seals, and stamps in source text should be mentioned using square brackets. It gives examples such as [seal] and [stamp]. The guideline was accessed in January 2026; its current edition and publication date aren’t established by the accessible page view, and its advice isn’t a universal legal requirement.
A bare label is only one possible treatment. The same NZSTI guideline permits a translator to render legible text inside the stamp in square brackets or explain the stamp’s content in a note. Those approaches give a reader more information than [stamp] alone when the wording is clear and relevant.
For example, a translator might use [stamp: received by the civil registry] if the mark’s words can be read and the recipient needs them. The exact wording should reflect what the source says, not an assumption about what the issuing office usually stamps. A round impression with no readable text might instead be described as [round seal, text illegible].
| What appears on the source | Possible translation treatment | When the treatment helps |
|---|---|---|
| A legible stamp with meaningful text | Translate the text in square brackets | The wording identifies an action, authority, or status |
| A seal whose presence matters but whose words don’t | Add a concise label such as [seal] |
The recipient needs to know a seal is present |
| A partly readable impression | Translate readable portions and mark the rest illegible | The visible wording carries information, but part can’t be read |
| A mark with useful context not clear from a short label | Add a translator’s note | The reader needs a brief explanation of the mark |
| An image or impression the recipient explicitly asks to see | Include or preserve an image if the required format allows it | A description alone won’t meet the stated instruction |
Those examples are options, not interchangeable labels. A note shouldn’t silently turn the translator’s interpretation into source text. Make the distinction visible: square brackets can mark text or a description supplied by the translator, while a separate note can explain a feature without pretending that the explanation was printed on the document.
A practical example is a birth certificate with a legible registry stamp and a faded circular seal. The registry stamp may contain words worth translating, while the seal’s unreadable lettering can be identified as illegible. A transcription that guesses the seal’s wording from the issuing office’s name creates false certainty.
Watch out: don’t omit a mark merely because it looks decorative. If you’re unsure whether it carries meaning, flag it for review and check the recipient’s instructions. For guidance on older Soviet-era formats and overlapping impressions, see translating pre-1991 Soviet documents.
What does the receiving organization need?¶
The receiving organization sets the practical target: its own acceptance rules may be more specific than a general professional guideline. Requirements for official translations differ between countries and legal systems, according to the Institute of Translation and Interpreting (ITI). That makes a single universal rule for every source stamp unsafe.
Ask for clear instructions before you translate, especially about certification and seals. ITI puts it plainly:
“ITI recommends that you obtain clear instructions regarding certification and the use of seals from the organisation requesting the translation, so you can discuss this with your chosen translator.”
The practical point is simple: don’t treat “certified translation” as a complete specification. Ask whether the recipient wants source-stamp text translated, a short description, an image, a particular page layout, or a translator’s own stamp or signature. A request for one type of mark doesn’t automatically answer what to do with the other.
What to ask before work starts¶
Send the requester a short list of questions. Keep the answers with the job instructions so a reviewer can see what the translation was prepared to satisfy.
- Which language and certification format do you accept? “Certified” means different things in different systems. In the UK, for example, ITI notes that there isn’t a sworn-translator system like those found in civil-law countries such as France, Spain, Germany, and Italy.
- Do you require text inside every source stamp to be translated? If the requester says yes, establish how they want unreadable portions marked.
- Do you require stamp images to appear in the translation? Ask whether a text description is enough or whether they expect a visual reproduction.
- Do you require the translator to sign, date, stamp, or initial the translation? Those are requirements about the translation’s certification, not necessarily about the source marks.
- Will you accept a translation made from a scan or electronic copy? Recording the source format can make the process transparent.
- Does the document need an apostille or other separate authentication? A translator’s certification and an apostille serve different purposes.
A message from a receiving organization may be brief. Save it anyway. If the requester gives no specific instruction, use a consistent, transparent convention, and don’t describe that convention as a rule the organization has approved.
USCIS and full translations¶
For documents submitted to USCIS, 8 CFR §103.2(b)(3) requires a full English translation of a foreign-language document. The translator must certify that the translation is complete and accurate and that the translator is competent to translate into English. The subsection doesn’t prescribe a special method for rendering stamps.
That distinction matters. The federal rule addresses a full translation and the translator’s attestations; it doesn’t say that every source seal must be reproduced as an image, or that a particular bracket notation must be used. Check the current e-CFR and any form-specific instructions before filing because the cited regulation was accessed in January 2026.
A document with a foreign-language stamp still needs a considered translation. If the stamp contains words, leaving them out may conflict with the idea of a full translation. But don’t turn this into a claim that USCIS mandates a specific visual treatment: the subsection doesn’t do that.
For further country-specific context, see the guides to USCIS translation requirements and certified, sworn, and notarized translations.
Which documents and marks should you check?¶
Start with every visible mark on the source, not just the large, obvious seal. Official documents can carry several kinds of impressions, and each may serve a different purpose. A stamp’s size or color doesn’t tell you whether its wording matters.
| Source feature | What to check | What to record |
|---|---|---|
| Official seal or stamp | Is the wording legible? Does it name an authority or action? | Translate readable wording, use a concise bracketed label, or add a note |
| Fee stamp | Does it show a payment, value, or office? | Account for it using the recipient’s requested level of detail |
| Registration or receipt mark | Does it contain a date, number, or status? | Preserve legible information and its relationship to the document |
| Handwritten entry crossing a stamp | Can any part be read? Is text crossed out? | Translate readable content and describe relevant cancellations |
| Embossed or faint impression | Can you distinguish its shape or text from the scan? | Describe only what you can verify; request a clearer source if necessary |
| Apostille | Is it on the original document or another item? | Keep its authentication role separate from translation certification |
| Translator’s certification mark | Does it identify the translator or certify the translation? | Apply the relevant certification instructions to the translated file |
The NZSTI guideline says legible portions of crossed-out text should be translated and the fact that they were crossed out noted. It also calls for a note when parts of a document are illegible. Applying that transparent approach to stamp text is safer than guessing, while the receiving organization’s specification still controls the final format. The guideline was accessed in January 2026.
A typical example is a certificate with a printed paragraph, a handwritten correction, and an official stamp partly obscuring the correction. The translator should preserve what can be read, indicate the crossed-out or obscured part, and avoid completing the hidden wording from context alone. If the stamp blocks text that affects a name, date, or status, ask for a better image or access to the original.
Scans, photocopies, and electronic files¶
A scan can make source details harder to distinguish. Low contrast, compression, cropping, glare, and a seal that overlaps typed text can all affect legibility. A translator may be able to read the body of a document while still being unable to make out lettering around a seal.
AUSIT’s Best Practices for the Translation of Official and Legal Documents, a November 2024 document accessed in January 2026, recommends an end note describing the type of source submitted. Its examples include [Translated from an electronic copy] and [Translated from a hard copy]. A note about source format can tell a reviewer what the translator actually examined.
For a scan, record the format when it matters, then assess each stamp on its own. Don’t claim that an illegible seal was verified against an original if the translator only saw a scan. If the scan is too poor to support a reliable reading, ask the requester for a clearer copy instead of filling gaps from general knowledge.
A document can also contain multiple versions of the same mark: a stamp on the scanned page, a seal added to a later certification page, and a translator’s stamp on the translated file. Keep each one attached to the correct source. The source marks belong to the document’s contents; the translator’s own mark belongs to the certification process.
For manuscripts and archival records, stamps may sit alongside abbreviations or handwritten entries. The workflow for translating Soviet labor books offers related context for handling layered records without flattening distinct marks into one vague description.
Translate, describe, or reproduce the mark?¶
Choose the least ambiguous presentation that meets the recipient’s instructions. Translation captures the words, description records what the mark looks like or does, and reproduction gives the reader an image of the mark. One method may be enough, but some documents call for a combination.
Translate the words¶
Translate legible text when it communicates a relevant fact, such as an issuing office or a registration action. Use square brackets if that’s the convention selected for distinguishing translator-supplied text from the source’s main text. NZSTI supports translating text inside a source stamp in square brackets.
A useful rendering stays close to the source. If a stamp says that an application was received, translate that wording; don’t expand it into a claim that the application was approved. A stamp naming an office doesn’t prove that the office authenticated every statement on the page.
Where a mark contains a name, date, or identifier, check those details against the visible source instead of relying on familiarity with the issuing authority. The translator can explain uncertainty, but shouldn’t silently standardize unclear text into a definitive answer.
Describe the mark¶
A description helps when a reader needs to know that a mark exists but its wording is unreadable, irrelevant, or not requested. [seal] is the short example NZSTI gives. A more informative description might state that a round seal overlaps a signature, but only if that visible feature helps the recipient understand the page.
Use a note when a description needs context beyond a short bracketed label. Keep notes factual and clearly separate from the document’s own content. A description such as “official seal of the issuing registry” is appropriate only if the source supports that identification; don’t infer the issuing body from a logo or the certificate’s general appearance alone.
Reproduce the mark as an image¶
An image can preserve visual evidence, but it doesn’t replace a readable translation when the recipient needs the stamp’s meaning. Reproduction may also be impractical if the document must be reflowed, if the impression is faint, or if the receiving organization asks for text rather than an image.
Don’t assume that inserting a cropped seal into a translated page will make the translation more acceptable. A crop can remove surrounding text or obscure the mark’s position on the original. If a recipient requests reproduction, confirm whether it wants the entire page, a detail image, or both, and make sure the translated text still accounts for the mark.
| Method | What the reader gets | Main risk | Best next check |
|---|---|---|---|
| Bracketed translation | The readable meaning of the mark | Brackets can be mistaken for text printed on the source if the convention isn’t clear | State the notation convention where needed |
| Bracketed description | Notice that a mark is present | A short label may leave meaningful wording unexplained | Check whether the recipient needs the stamp’s text |
| Translator’s note | Context about position, condition, or source format | A note can blur observation and interpretation | Separate what is visible from what is inferred |
| Image reproduction | A visual record of the impression | Cropping or layout changes can misrepresent context | Confirm the format the recipient accepts |
| Combination | Text plus visual or contextual information | Repetition can clutter the translation or create inconsistency | Choose one purpose for each element |
A common practical case is a seal with a clear outer ring but an unreadable center. A translator may describe the seal’s presence and translate any legible words without claiming to know the center text. If the requester needs the image, preserve it in the agreed format and keep the description consistent with what the image shows.
Watch out: don’t use a translated stamp as though it were a new official stamp. Bracketed words in a translation communicate source content; they don’t authenticate the source or grant the translation legal status.
How should a translator certify the translation?¶
A translator’s certification statement, signature, initials, or stamp identifies the translation under a particular process. Those marks aren’t the same as seals already present on the source document. Confusing the two can leave the translated content incomplete while creating a false impression that a source mark has been verified.
The GOV.UK guidance on certifying a document says a translator certifying a document not written in English or Welsh should confirm in writing that the translation is true and accurate, give the translation date, and provide their full name and contact details. The page doesn’t list a translator seal as a mandatory element.
GOV.UK states:
“If you need to certify a translation of a document that’s not written in English or Welsh, ask the translator to confirm in writing on the translation: - that it’s a ‘true and accurate translation of the original document’ - the date of the translation - their full name and contact details”
That instruction describes the certification statement, not the way a source seal must be translated. A translation prepared for a different jurisdiction may follow different rules, so don’t apply the UK guidance as a universal template.
AUSIT’s November 2024 best-practices document, accessed in January 2026, recommends signing and dating the translation and suggests stamping or initialling each page. It also says a translator’s stamp, when used, should include the translator’s name, translation date, certification details, and language pair. The document says the stamp isn’t compulsory in its guidance context. Follow the recipient’s rules rather than turning professional guidance into a legal requirement.
ITI also describes a certified translation as one that attests to the translation being true, complete, and accurate. Its guidance says each translation page should be stamped and/or initialled by the translator or certifying authority to guard against tampering or misuse. That advice concerns marks on the translation; it doesn’t create a requirement to reproduce every source-document seal.
ChatsControl can help with the document-review stage when a team needs to inspect layout and source content together. In ChatsControl, a translator can upload a document, review the source and translation side by side, and use the highlighted translated text to check how content maps across. That can support a human check of whether a stamp was carried into the translation, but it doesn’t determine the receiving authority’s rules or replace a human certification step.
Apostille is a separate question¶
An apostille is a certificate that verifies the authenticity of a signature and helps a document be recognized in states that apply the Hague Convention; it doesn’t endorse the document’s content. ITI distinguishes apostille from translation certification and says the original document generally bears the apostille.
ITI also says a translation can’t be sealed with an apostille unless it carries a declaration endorsed by a notary public. Requirements for a particular destination still need confirmation with the receiving authority. A translator shouldn’t treat an apostille as a replacement for translating a stamp, certifying a translation, or following instructions about the source document.
How to brief and review a stamp-heavy translation¶
A short written brief helps the translator, reviewer, and production team make consistent decisions. Use the checklist below before the translation begins, then return to it during final review. Keep recipient instructions and any decisions about unreadable text with the job file.
Job brief checklist¶
- Identify the destination and recipient. Record the organization that will review the translation and the country or process involved.
- Request the recipient’s current requirements. Ask about certification, signature, translator seal, page initials, source-seal images, and any required wording.
- Record the source format. Note whether the translator received a hard copy, scan, or electronic copy. AUSIT recommends describing source format in an end note where relevant.
- List each visible stamp and seal. Give each mark a temporary label, such as “upper-right registry stamp” or “seal overlapping signature.”
- Set a notation convention. Decide how square brackets, explanatory notes, and illegibility markers will appear.
- Mark uncertain readings. Separate clear text from unclear text, and ask for a better source when a key detail can’t be read.
- Keep certification separate. Identify which signature, stamp, or statement belongs to the translator or certifying authority rather than the source document.
- Run a final completeness check. Compare the translation against the whole source page, including edges and areas partly covered by other marks.
A simple mark log can prevent two translators from describing the same impression differently. Use a table like this alongside the source file:
| Mark ID | Location and appearance | Legible text | Chosen treatment | Open question |
|---|---|---|---|---|
| A | Upper-right rectangle | Office name and received status | Translate in brackets | None |
| B | Round seal over signature | Outer text partly legible | Translate readable words; mark the rest illegible | Ask for a clearer copy |
| C | Lower margin | Date stamp | Translate date and label | Confirm recipient’s date format |
The sample entries show a format only; they don’t describe a real document. A mark log is especially useful when the scan has overlapping text or multiple impressions, because a reviewer can trace each translation decision to a location on the source.
Final review: what to verify¶
Compare source and translation in the same order, moving from the main text to marginal marks. Check that every relevant mark has a corresponding translation, description, or explicit reason for omission under the agreed instructions. Then check that no note claims more than the source reveals.
Review these details closely:
- Names and titles inside seals match the visible letters.
- Dates and numbers are readable and have not been reconstructed from context.
- Crossed-out wording is handled transparently, following the NZSTI guidance accessed in January 2026.
- Unreadable text is marked as unreadable rather than replaced with a guess.
- Brackets and notes consistently show which wording the translator supplied.
- Any reproduced image retains enough surrounding context to identify its place on the page.
- The translator’s certification mark is clearly separate from source-document marks.
- The certification statement matches the recipient’s actual instructions.
The standalone QA validator in ChatsControl can check a translation for numbers, names, terminology, and omissions. A translator can use it as an additional review aid after preparing the draft. The tool can’t determine whether an unclear seal says a particular word or whether a specific authority will accept an image; those decisions still require source review and recipient instructions.
Watch out: an automated check can flag a mismatch, but it can’t recover text hidden by a stamp or certify that a document is authentic. If the source doesn’t support a reading, leave the uncertainty visible and request a better copy or instructions.
Common problems and regional differences¶
Most stamp-related problems come from treating a general convention as a recipient’s rule. A bracketed description can make a translation clear, but it doesn’t guarantee acceptance. Certification requirements also vary: ITI explains that official translation requirements depend on each country’s legal system.
A UK translator may follow GOV.UK’s written accuracy statement, date, name, and contact details guidance without adding a translator stamp as a mandatory element. A translation intended for another system may need different certification or a different process. The point isn’t to pick one country’s practice as the default; it’s to establish what the recipient wants before finalizing the job.
| Situation | Don’t assume | Better action |
|---|---|---|
| A recipient asks for a certified translation | Every country defines certification the same way | Ask what statement, signature, stamp, or professional status it requires |
| A source has a large round seal | Its lettering is decorative or can be omitted | Check whether it contains readable wording and account for it |
| The seal is hard to read | The issuing office’s usual wording proves what’s there | Mark unreadable text and request a clearer source if the detail matters |
| The translation has a translator stamp | The source seals have therefore been translated | Review source marks separately from certification marks |
| A document carries an apostille | The apostille certifies the translation’s content | Confirm the apostille’s role and the recipient’s authentication instructions |
| The job uses a scan | The translator has checked the original | State the source format accurately and identify scan-related limits |
A frequent omission is a small registration mark at the edge of a page. The main certificate may be fully translated while the mark that records receipt or registration is ignored. A final visual sweep of the entire page catches that problem more reliably than proofreading only the translated paragraphs.
Another common mistake is to describe a mark as “official” when the source gives no basis for identifying it. Describe what can be seen: a round seal, a rectangular stamp, a handwritten entry, or a legible office name. Keep conclusions about the mark’s legal effect out of the translation unless the source or the receiving organization supports them.
The distinction between a translator’s mark and an apostille causes another avoidable error. ITI says an apostille verifies a signature rather than endorsing document content, and notes that the original document generally bears it. A notarial declaration may be relevant if someone wants an apostille attached to a translation, but the destination’s requirements still need to be checked.
For documents that require a notarial process, keep the physical assembly instructions separate from decisions about source-stamp wording. The guide to how notarized translations are stitched covers the attachment question. A stitched translation still needs a clear account of relevant marks on the source.
FAQ¶
Should translators translate the text inside every stamp and seal?¶
Account for each relevant source mark, but the exact treatment depends on the recipient’s instructions. NZSTI guidance accessed in January 2026 allows a bracketed label, a translation of legible text in brackets, or an explanatory note; it isn’t a universal legal rule.
How should an illegible stamp be shown in a certified translation?¶
Translate the parts that can be read and identify the unreadable portion as illegible. NZSTI guidance accessed in January 2026 calls for notes when document parts are illegible; don’t fill gaps by guessing.
Should the original stamp or seal be reproduced as an image in the translation?¶
Not automatically. A bracketed description or translation may be enough, but ask the receiving organization whether it requires an image, a particular layout, or a translated description.
How do translation certification stamps differ from stamps on the source document?¶
A source stamp is part of the document being translated. A translator’s stamp or signature relates to certification of the translation, and requirements for that mark vary by recipient and jurisdiction.
What does USCIS require for translations containing foreign-language stamps?¶
Under 8 CFR §103.2(b)(3), USCIS requires a full English translation and the translator’s certifications of completeness, accuracy, and competence. The subsection doesn’t set a special method for rendering stamps; check the current e-CFR and form-specific instructions before filing.
Does a translator need to stamp every page?¶
The answer depends on the receiving organization’s requirements. ITI recommends stamping and/or initialling each page in its guidance, while AUSIT’s November 2024 document recommends signing and dating and suggests stamping or initialling pages; neither point should be treated as a universal legal rule.
Can an apostille certify the content of a translated seal?¶
No. ITI describes an apostille as verification of a signature, not an endorsement of document content. The original document generally bears the apostille, and destination-specific instructions should be confirmed with the receiving authority.
What should I do if the recipient gives no instructions about seals?¶
Ask the recipient for written guidance on certification and the use of seals, as ITI recommends. If no further instructions are available, use a consistent, transparent notation, identify unreadable text, and avoid claiming that your chosen format is universally accepted.