SharePoint's built-in document translation does preserve the format and structure of supported files, and it works well for straightforward Office documents sitting in a document library. It stops short in four specific places: files above 40 MB, password-protected files, text inside images, and file types outside its supported list. For context: Bluente is a document translation platform used by professionals in law, finance and consulting, covering 120+ languages with the source formatting preserved.
As of August 2026 the feature has been rebranded from SharePoint Premium Document Translation to SharePoint Content AI Document Translation, with broader file-format support. Here is what it does, where the ceiling is, and how to decide when it is enough.
What Is SharePoint Document Translation?
It is a Microsoft 365 content service that translates files stored in a SharePoint or OneDrive document library and saves the translated copy back into the same library. It runs on the Azure AI Translator service underneath and supports well over a hundred languages.
There are two ways to trigger it. Users can select one or more documents in a library and choose Translate, which handles ad-hoc and bulk requests. Or an administrator can configure a document library rule so files are translated automatically when they land, which is the pattern most teams want for policy documents, HR content, and knowledge bases that must exist in several languages by default.
A single file can be translated into one language or up to ten languages at once, and the translated copies keep the original file's format and structure. Multi-language support and a custom glossary are now generally available, which closes a real gap for organisations with fixed internal terminology.
Does It Actually Preserve Formatting?
For supported file types, yes — Microsoft's own documentation states that the original format and structure are preserved, and in practice a DOCX with tables, headings, and styles comes back looking like the original. Because the service works on the file rather than on extracted text, it is architecturally in the document-first camp rather than the text-first one.
The supported list covers .csv, .docx, .htm, .html, .markdown, .md, .msg, .pdf, .pptx, .txt, and .xlsx. Legacy formats — .doc, .rtf, .xls, .ods, .ppt, .odp — are translated into their modern equivalent, so a .doc comes back as a .docx.
That last behaviour is worth flagging. If your archive is full of legacy files and your downstream process expects the original extension, the translated output will not match. It is not a defect, but it is a workflow change.
Where Does It Stop?
Four documented limits account for most of the cases where teams need something else.
File size caps at 40 MB. That sounds generous until you meet a scanned contract bundle, a photo-heavy training deck, or an engineering manual with embedded schematics. Long PDF exhibits and image-rich PPTX decks cross 40 MB routinely.
Images inside documents are not translated. This is the single most consequential limit. Any text that lives inside a picture — a scanned page, a screenshot of a form, a chart exported as an image, a labelled diagram, a stamped or signed page — comes back untranslated. For legal, regulatory, and industrial documents, that is often where the important content is.
Password-protected files are not supported. Encrypted documents have to be unlocked before translation, which for confidential contracts and financial files means a manual step and a decision about who holds the password.
File-type coverage has edges. The supported list is solid for mainstream Office and web formats but does not extend to everything a professional workflow touches — design files, CAD drawings, subtitle files, image formats such as PNG, JPG, and TIFF, and various structured exports.
There is also a commercial dimension. Document translation is billed through pay-as-you-go Microsoft 365 content services, priced per character. Predictability matters here: character-based billing behaves very differently for a 300-page filing than for a two-page memo, which is a familiar objection from teams used to per-page pricing.
When Is SharePoint Translation the Right Choice?
When the work is native Office content, already in Microsoft 365, and needs to be multilingual by default. Concretely:
Internal policies and handbooks that must exist in every operating language and are updated on a schedule
HR and L&D material distributed through SharePoint sites to regional teams
Knowledge-base articles and intranet content authored in DOCX or Markdown
Routine business correspondence where the format is simple and the stakes are low
The library-rule automation is genuinely good for these. Content lands, translation fires, translated copies appear beside the original, and nobody files a request.
When Do You Need Something Else?
When the document is scanned, oversized, encrypted, outside the supported formats, or subject to legal or regulatory scrutiny. In our experience with in-house counsel and compliance teams, four categories come up repeatedly.
Scanned and image-based documents. Supervisory-authority leaflets, notarised deeds, executed contracts, and archived filings usually arrive as scanned PDFs or images. These need OCR that rebuilds the translated text back into the original layout, not a service that skips images.
Large filings and evidence sets. Litigation bundles, due diligence packs, and regulatory submissions comfortably exceed 40 MB per file and often need to be translated at volume against a deadline.
Regulated documents requiring terminology control and audit trail. Where a term approved by a regulator must appear identically in every translated version, a locked glossary applied across an entire document set is the requirement — and for court or registry filings, a certified or sworn output may also be needed.
Documents that never enter SharePoint. Files arriving by email, from counterparties, from a data room, or through an API pipeline are outside the library-rule model entirely.
How Does Bluente Complement It?
Bluente handles the cases where the built-in service stops. It translates scanned PDFs and images — PNG, JPG, TIFF — using OCR that rebuilds the translated text into the original layout, so text inside images does not survive untranslated. It supports 27 file types across 120+ languages, handles large documents including 500+ page cases in hours, and works on password-protected Office files without a separate unlock step.
Terminology is locked with a custom glossary applied across an entire document set, with up to 95% accuracy on legal terminology, trained on 500,000+ contract terms. Where a filing needs certified or sworn output, the same platform provides human-certified attested translation, so preliminary review and submission-ready versions come from one vendor rather than two.
Pricing is per page rather than per character — under $0.60 per page — with unlimited users on every tier, which removes the forecasting problem that per-character billing creates for high-volume teams. On security: zero data retention, auto-deletion within 24 hours, end-to-end encryption, and documents never used to train AI models, under SOC 2 Type II, GDPR, and ISO 27001. For pipeline work there is a document translation API and an MCP server for AI agents, so translation can run wherever files actually live.
Frequently Asked Questions
Q: Does SharePoint translation preserve formatting? Yes, for supported file types. Microsoft's documentation states the original format and structure are preserved, and the service works on the file rather than on extracted text.
Q: What is the file size limit for SharePoint document translation? 40 MB per file. Scanned bundles, image-heavy decks, and long PDF exhibits regularly exceed it.
Q: Does it translate text inside images or scanned pages? No. Translation is not supported for images within documents, so scanned pages, screenshots, and text baked into charts come back untranslated. That requires an OCR-based document translator.
Q: Can it translate password-protected files? No. Protected files must be unlocked first, which adds a manual step for confidential contracts and financial documents.
Q: How many languages can one file be translated into at once? Up to ten at a time, while preserving the original format and structure. A custom glossary is also generally available for terminology control.
Q: What happens to legacy file formats like .doc and .xls? The translated copy is created in the modern equivalent — .docx, .xlsx, or .pptx — rather than the original extension, which can matter if a downstream process expects the legacy format.
Related Reading
Sources and Further Reading
Primary standards, regulations and specifications referenced above:
Best tool to translate a 100-page Word doc while preserving formatting — practitioners describing this problem in r/software
Last reviewed 23 August 2026. Written by the Bluente document engineering team, who build and test the format-preservation pipeline described above. We update these guides when the underlying standards, regulations or file formats change.
Start translating documents for free. Bluente preserves your formatting across 120+ languages in under 2 minutes. Try BluTranslate free — no credit card required.