Translations & multilingual sites (WPML, Polylang) Free
FileDeck ships its front end in nine languages, documents and categories translate like any content, and a bundled wpml-config tells WPML and Polylang how document data behaves.
Updated September 15, 2026
FileDeck stores documents as ordinary WordPress content — a post type and two taxonomies — which is exactly what translation plugins are built to handle. Documents and categories translate like posts and categories do, and every piece of FileDeck’s own interface text is internationalised.
What the bundled configuration does
FileDeck ships a wpml-config.xml, the standard declaration file that WPML,
Polylang and compatible plugins all read. It declares:
- the document post type and both taxonomies as translatable;
- file references (the attached file, external URL, size, type) as copied to translations — a French translation of a policy points at the same PDF, it doesn’t demand a second upload;
- lifecycle settings (visibility, expiry, download limits) as copied, so a translation is governed exactly like its original;
- the download counter as ignored — each language’s copy counts its own downloads.
Bundled interface translations
Since 2.94.0 the plugin ships translations of the strings a visitor reads in a library — the search box, the filters and their "All categories" summaries, "No documents match your search", "Download", the per-page dropdown, the document count, the lead-capture and terms prompts, the share menu. Since 2.98.1 they also cover the "Document Category" and "Document Tag" names on category and tag archive pages, and the notices Pro and AI tier features show visitors: the superseded notice, the "Attached documents" and "Related documents" headings, the read-and-confirm prompt, the empty collection and document changelog messages, and the placeholder choice at the top of dropdown fields on the front-end submission form. The bundled languages:
| Language | Locale |
|---|---|
| German | de_DE |
| Spanish | es_ES, es_MX |
| French | fr_FR, fr_CA (since 2.97.0) |
| Hungarian | hu_HU |
| Italian | it_IT |
| Polish | pl_PL |
| Portuguese (Brazil) | pt_BR |
| Slovak | sk_SK |
| Chinese (Simplified) | zh_CN |
There is no installation step: WordPress picks the file that matches Settings → General → Site Language (or the visitor’s language on a multilingual site). A community language pack from translate.wordpress.org, where one exists, is loaded together with the bundled file (since 2.99.0): the pack’s translations take priority, so improvements contributed there reach your site first, and the bundled file supplies whatever the pack does not cover, Pro and AI tier text included.
These are machine translations checked for placeholders and length, not native copy. If a string reads wrongly in your language, tell us on the support page or correct it at translate.wordpress.org — both routes land in the next release. Pro and AI tier strings are not on translate.wordpress.org, because the free plugin does not contain them, so report those on the support page.
Admin screens are mostly in English. The Documents menu, the Document Fields (Pro), Acknowledgments, Smart Collections and AI Index (AI tier) screens, and the Supersede, Attached documents and Read & confirm boxes follow your admin language, because they share text with what visitors see; the other admin screens do not. A community language pack covers whatever its contributors have translated.
The footer on a watermarked PDF (AI tier) is translated but printed in plain ASCII, so accented letters become plain ones where the server can transliterate them; otherwise, and for languages such as Chinese, the footer stays in English. The emails transmittals send (AI tier) stay in English. The Document Library page FileDeck creates on first activation is titled in the site’s language when FileDeck has a translation for it (since 2.99.0); you can rename it like any page.
Translating FileDeck yourself
The plugin ships a translation template, languages/filedeck.pot, which
Loco Translate, Poedit and similar tools read to list the strings to
translate. It includes the text the library builds in the browser — the
"Copy link" button, "Load more", the page buttons, the search palette —
and the block editor’s labels.
With Loco Translate, open Loco Translate → Plugins → FileDeck, add
your language, and save the file to the Custom location
(wp-content/languages/loco/plugins/), where plugin updates leave it alone.
Poedit users can create a new translation straight from the .pot.
The honest boundary
Translation-ready is a precise claim and we keep it precise: the data model and interface are fully prepared, and the declaration file covers the meta behaviour. What we have not done is certify every workflow inside WPML’s own UI (translation management jobs, string-translation edge cases). If you run FileDeck on a multilingual site and hit anything odd, say so on the support page — multilingual reports get fixed with priority precisely because this surface is hard to test in the lab.
Still stuck? Email support@getfiledeck.com.