Skip to main content
Hyperlocalise Platform brings multilingual content into one workspace. Native projects accept application resource files, documents, images, video, and Office files, but translation and editing differ by format. Upload support alone does not mean a file supports automatic translation or segment editing.

​
Native project file support

The table describes the native source-upload and file workflow. Connected TMS projects follow the provider’s capabilities. Office files are not handled by automatic file translation jobs. Open File view and upload or edit the translated file there. Other translation workflows require an enabled provider and the relevant workspace access. A listed extension still needs valid content for its parser or viewer.

​
Choose a format guide

For a complete Platform workflow, start with one of these tutorials: Some tutorials use repository preprocessing or CLI translation. In particular, Android .xml and gettext .pot are not listed in the native source-upload extension set above. Follow each tutorial’s preparation and delivery path rather than assuming a CLI-supported extension can be uploaded directly. For local translation, the all-in-one Hyperlocalise CLI has its own file-format guides, including additional formats such as Java properties, PHP, Fluent, and RESX.

​
Upload, translate, review, and export

  1. Create a project and choose source and target locales.
  2. Upload your files. The native upload screen accepts up to 10 files per batch.
  3. Start translation, or use the manual Office workflow above.
  4. Review the result in the view available for that file family.
  5. Download translated files and check them in the consuming application.
Uploading alone does not start translation unless you configure a matching source-upload automation.

​
Is a queue export the same as a translated file?

No. A Content Editor queue export contains filtered segments as CSV, TMX, XLF/XLIFF, or XLSX, up to 5,000 matching segments. It is useful for review and handoff. Use the project’s Download translations action for complete target files. Document, image, video, and Office file views work with stored files rather than a segment queue.

​
Does Platform support every CLI or TMS file format?

No. Local CLI parsing, native Platform uploads, and provider imports are separate contracts. Use the table above for native uploads, the provider’s import rules for connected projects, and the CLI format overview for local translation. Supporting an export format does not imply a matching source-upload format. If an accepted file cannot open, check upload troubleshooting.