Most real projects do not have a target language. They have a list. The same benefits letter goes into Spanish and Haitian Creole; the same manual goes into Canadian French and US Spanish. Until this week, Fily made you treat that list as separate projects: upload, pick a language, launch, and start over for the next one.
How it works
Under the target language there is a link: “Add more languages”. Each language you add appears as a chip, with a running count of how many languages the launch will produce. When you launch, Fily creates one job per language from the same upload.
They are real jobs, not copies of one. Each resolves its own glossary, style guide, translation memory and pipeline for its own language, exactly as if you had launched it alone. Your French glossary does not leak into the Spanish job, and a language with no glossary simply runs without one.
- The quote shows the cost per language and the total before you launch.
- The job list marks each job as part of a set, “1 of 3”, “2 of 3”.
- You get one email when every language is done, not one per language.
- “Download all languages” returns a single ZIP with one folder per language.
All or nothing
A launch with three languages is checked as one thing. Credits are checked against the total, not the first language, so you never end up with two languages running and a third one refused. If anything fails while the set is being created, the languages that were already created are cancelled before they start. You either get the whole set or none of it.
Everywhere you launch work
The same picker is in document, audio and video jobs. Clients ordering through the portal can choose several languages in one order, see the estimate per language, and receive one “order ready” email for the set. The API takes a list of target languages on the same endpoints as before, and every webhook says which language and which set the job belongs to.
Jobs that read from and deliver to a shared folder get a subfolder per language, so three languages of the same file do not overwrite each other.
What did not change
If you only need one language, nothing is different: the request Fily sends is exactly the one it sent before. Rates do not change either. Each language is charged what it would cost on its own.
Want this in your workflow? Try Fily with one file — no card, no demo form.