Exports

Babelize offers flexible export options to integrate translations into your workflow. This guide covers all available export methods and formats.

Export Methods

Dashboard Export

The quickest way to download translations:

1. Open your project
2. Select the translated file
3. Click Export
4. Choose your format
5. Click Download

Bulk Export

Export multiple files at once:

1. In a project, select multiple files using checkboxes
2. Click Export Selected
3. Files are packaged as a ZIP archive
4. Download the archive

API Export

Programmatically retrieve translations:

curl -X GET "https://api.babelize.app/v1/jobs/{job_id}/result" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -o translated_file.json

Export Formats

Same as Source

The default option preserves your original format:

Alternative Formats

Convert during export for specific use cases:

CSV Export Structure

CSV exports use this structure:

key,source,target,context
greeting,Hello,Hola,UI string
farewell,Goodbye,Adiós,UI string

Columns:

• key: The original key or path
• source: Original text
• target: Translated text
• context: Extracted from comments or metadata

Export Options

Include Metadata

Add translation metadata to exports:

{
  "_metadata": {
    "source_language": "en",
    "target_language": "es",
    "translated_at": "2024-01-15T10:30:00Z",
    "model_version": "2024.1.0"
  },
  "greeting": "Hola",
  "farewell": "Adiós"
}

Flatten Nested Keys

Convert nested structures to flat keys:

Original:

{
  "messages": {
    "greeting": "Hola"
  }
}

Flattened:

{
  "messages.greeting": "Hola"
}

Include Source

Include source text alongside translations:

{
  "greeting": {
    "source": "Hello",
    "target": "Hola"
  }
}

Project-Level Export

Export entire projects for backup or migration:

1. Go to Project Settings
2. Click Export Project
3. Select what to include:
   • Translations
   • Glossary
   • Settings
   • History (optional)
4. Click Generate Export
5. Download when ready

Project exports create a ZIP containing:

project-export/
├── manifest.json
├── glossary.json
├── settings.json
└── translations/
    ├── en-to-es/
    │   ├── file1.json
    │   └── file2.json
    └── en-to-fr/
        ├── file1.json
        └── file2.json

Scheduled Exports

Team plans support scheduled exports:

1. Go to Project Settings → Scheduled Exports
2. Click Add Schedule
3. Configure:
   • Frequency (daily, weekly, monthly)
   • Format
   • Destination (email, webhook, cloud storage)
4. Save the schedule

Cloud Storage Destinations

Connect cloud storage for automatic uploads:

• Amazon S3
• Google Cloud Storage
• Azure Blob Storage

Configuration requires providing credentials with write access to your bucket.

Export Limits

Encoding and Formatting

All exports use:

• UTF-8 encoding
• Unix-style line endings (LF)
• 2-space indentation for JSON/YAML

Configure formatting preferences in Project Settings → Export Formatting.

Export History

Track all exports:

1. Go to Project Settings → Export History
2. View list of all exports with:
   • Timestamp
   • Format
   • File count
   • Download link (available for 7 days)