Humlens Beta
Words and pictures · File formats

Bring files in the format you have. Get them back the same way.

String files, documents and media go in as they are and come out in the same structure, ready for your code, store or CMS.

JSON YAML CSV XML PROPERTIES PNG MP4 MP3 Humlens API + webhooks locales/ ├ en.json ├ es.json ├ hi.json └ ja.json media/ ├ promo.es.mp4 └ promo.hi.mp4 Repo synced
How it works

Four steps, start to finish

  1. 1

    Import

    Upload a file or sync a repository.

  2. 2

    Localize

    Translate and review in the app.

  3. 3

    Export

    Same format, one file per language.

  4. 4

    Automate

    Use the API and webhooks to keep it running.

What it does

File formats, in detail

Everything runs in your own cloud, on the AI provider keys you bring, with your glossary applied at every step.

01

String files

JSON, YAML, properties, CSV and XML, exported in the format they came in.

02

Images

Common web and marketing image formats, exported per language.

03

Audio and video

Upload media; get dubbed files and per-language subtitle files back.

04

Repositories

Sync string files with GitHub, GitLab or Bitbucket.

05

API and webhooks

Push and pull files from your own scripts and CI.

06

Your storage

Files live in your S3 bucket, or the bundled MinIO.

Who it's for

Teams that use file formats

Developers

Locale files that drop straight back into the codebase.

Store owners

CSV product copy for bulk import into your store.

Media teams

Subtitles and dubbed files for each platform.

Questions

About file formats

Runs in your cloud on your own AI keys. How that works →

Is the file structure kept?

Yes. Exports use the same format and keys as the file you imported, one file per language.

We use a format that isn't listed.

Tell us which one. Most teams convert to JSON or CSV in their build step today.

See file formats on your own content.

Bring a file, a creative or a video. We'll run it through Humlens and show you how it deploys into your cloud.