Lingo.dev Localizer
Pricing
Pay per usage
Lingo.dev Localizer
Translate a single JSON/YAML/plain-text file into multiple languages using lingo.dev. Provide a URL, upload, or paste content and get one dataset row per language with translated text or a download URL. Perfect for fast i18n workflows, CI automation, and asset localization.
Pricing
Pay per usage
Rating
0.0
(0)
Developer

Iñigo Garcia Olaizola
Actor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
🤖 What does Lingo Localizer do?
Lingo Localizer translates a single file (JSON/YAML/plain text) or pasted content using the lingo.dev CLI. It produces one translated file per target language and stores the results in the dataset.
Two input modes:
- URL / Upload: The actor downloads the file, translates it, stores each translated file in the default key‑value store, and writes dataset rows with URLs.
- Direct content: The actor translates the pasted content and stores the translated content directly in dataset rows.
🚀 How to use the actor
- Choose an input source
- URL, Upload, or Direct content.
- Set source and target languages
- Example: source
en, targetses,fr.
- Example: source
- Run the actor
- One dataset row is created per target language.
💡 Use cases
- App UI strings stored in JSON/YAML for web or mobile projects.
- Videogame text packs and in‑game dialog files.
- Backend/email templates kept as plain text snippets.
- Marketing copy and product descriptions.
- Help center / FAQ content managed as flat files.
- Configuration-driven prompts for AI assistants in multiple languages.
📝 Input parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
inputSource | String | Yes | url, upload, or content. |
inputUrl | String | Conditionally | Public URL to a single JSON/YAML/plain-text file. Required if inputSource=url. |
inputUpload | String | Conditionally | Upload a single JSON/YAML/plain-text file. Required if inputSource=upload. |
inputContent | String | Conditionally | Paste content directly. Required if inputSource=content. |
sourceLanguage | String | Yes | Source language code (e.g., en). |
targetLanguages | Array | Yes | Target language codes (e.g., es, fr). |
lingoCommand | String | No | run (default) or i18n. |
lingoArgs | Array | No | Additional CLI arguments. |
lingoApiKey | String | Yes | lingo.dev API key used for authentication. |
Example input (URL):
{"inputSource": "url","inputUrl": "https://example.com/messages.json","sourceLanguage": "en","targetLanguages": ["es", "fr"],"lingoApiKey": "your_api_key"}
Example input (Content):
{"inputSource": "content","inputContent": "Hello world","sourceLanguage": "en","targetLanguages": ["es"],"lingoApiKey": "your_api_key"}
📦 Output
The dataset always has one row per target language.
If input source is URL/Upload, each row includes a URL to the translated file:
{"language": "es","url": "https://api.apify.com/v2/key-value-stores/.../records/OUTPUT_ES"}
If input source is Content, each row includes translated text:
{"language": "es","content": "Hola mundo"}