Excel (.xlsx) Import

Azbox supports Excel spreadsheets (.xlsx) for importing translations. This is ideal for teams that manage translations in spreadsheets or receive translations from external translators.

When to Use Excel Import

• 📊 Translations managed in spreadsheets
• 📧 Received translations from external translators
• 🔄 Migrating from another localization platform
• 📋 Bulk import from existing translation databases

File Format

Azbox expects a spreadsheet with:

• Header row — Column names in the first row
• Key column — Translation keys (identifiers)
• Language columns — One column per language

Basic Structure

Key	en	es	fr
welcome	Welcome	Bienvenido	Bienvenue
login	Log In	Iniciar Sesión	Connexion
logout	Log Out	Cerrar Sesión	Déconnexion

Supported Column Names

For the key column:

• key
• keyword
• string
• source
• source text
• source_text
• id
• string id
• identifier
• string_id

For language columns:

• Use your project's language codes (e.g., en, es, fr, de)
• Must match exactly with languages configured in your Azbox project

Complete Example

Create a spreadsheet like this:

keyword	en	es	fr	de
app_name	My App	Mi App	Mon App	Meine App
welcome_message	Welcome!	¡Bienvenido!	Bienvenue !	Willkommen!
login_button	Log In	Iniciar Sesión	Connexion	Anmelden
logout_button	Log Out	Cerrar Sesión	Déconnexion	Abmelden
settings	Settings	Configuración	Paramètres	Einstellungen
profile	Profile	Perfil	Profil	Profil
save	Save	Guardar	Enregistrer	Speichern
cancel	Cancel	Cancelar	Annuler	Abbrechen
delete	Delete	Eliminar	Supprimer	Löschen
confirm	Are you sure?	¿Estás seguro?	Êtes-vous sûr ?	Bist du sicher?

Save as .xlsx format.

How to Import in Azbox

Step 1: Prepare Your Spreadsheet

Ensure your Excel file has:

• ✅ Header row with column names
• ✅ A key/keyword column
• ✅ Language columns matching your project languages

Step 2: Open Import Dialog

Click Import in your project dashboard.

Step 3: Select Format

Choose Excel (.xlsx) from the dropdown.

Step 4: Import File

Click Import and select your .xlsx file.

Step 5: Review Results

Azbox shows:

• ✅ Keywords imported
• 🌍 Languages detected
• ⚠️ Warnings (missing translations, unmatched languages)
• ❌ Errors (if any)

What Gets Imported

Content	Imported	Notes
Key column	✅ Yes	Used as keyword identifier
Language columns	✅ Yes	Only if matching project languages
Empty cells	⚠️ Skipped	Warning generated
Unmatched languages	⚠️ Skipped	Columns not matching project languages
Multiple sheets	❌ No	Only first sheet is processed

Multi-Language Import

Unlike other formats, Excel import processes all languages at once:

┌─────────────┬──────────┬─────────────┬──────────┐
│   keyword   │    en    │     es      │    fr    │
├─────────────┼──────────┼─────────────┼──────────┤
│ welcome     │ Welcome  │ Bienvenido  │ Bienvenue│  ← All 3 languages
│ goodbye     │ Goodbye  │ Adiós       │ Au revoir│     imported at once
└─────────────┴──────────┴─────────────┴──────────┘

Automatic Language Detection

Azbox automatically detects language columns by matching header names with your project's configured languages.

Common Issues

"No language columns found"

Problem: Header names don't match project language codes.

Solution: Ensure column headers exactly match your project languages:

• ✅ en (if your project uses en)
• ❌ English (won't be recognized)
• ❌ EN (case-sensitive)

"No keyword column found"

Problem: No recognizable key column.

Solution: Rename your key column to one of: key, keyword, source, id, string.

Empty rows skipped

Problem: Rows without translations are skipped.

Solution: This is normal — only rows with at least one translation are imported.

Best Practices

1. Match language codes — Use exact codes from your Azbox project
2. Clean your data — Remove empty rows and formatting
3. Use first sheet — Azbox only reads the first sheet
4. Consistent keys — Use snake_case or camelCase consistently
5. No merged cells — Avoid merged cells in the spreadsheet

Template

Download a template to get started:

keyword	en	es	fr	de	pt

Or create your own with these columns.

Workflow Example

From Google Sheets

1. Create translations in Google Sheets
2. Download as .xlsx (File → Download → Microsoft Excel)
3. Import into Azbox

From External Translator

1. Send translator an Excel template with keyword + en columns
2. Translator adds new language column (e.g., ja)
3. Import completed file into Azbox

Bulk Migration

1. Export from old platform to Excel/CSV
2. Rename columns to match Azbox format
3. Import into Azbox

Crowdin Compatibility

Azbox's Excel format is inspired by Crowdin's XLSX format. If you have exports from Crowdin, they should work with minimal modifications:

Crowdin Column	Azbox Equivalent
Identifier	keyword or id
Source String	source
<Language>	Language code (e.g., es)

---

Related

• CSV Import — For comma-separated files
• JSON Import — For JavaScript projects