Product
Services
Solutions
BlogDocs
Back

Frequently Asked Questions (FAQ)

Find answers to the most common questions about Localit.io translation management system.

Getting Started

What is Localit.io?

Localit.io is a modern translation management system (TMS) designed to streamline localization workflows for developers, translators, and teams. It supports multiple file formats, integrates with popular development platforms, and offers AI-powered translation services.

How do I create my first project?

  1. Sign up for a Localit.io account

  2. Click "Create New Project" on your dashboard

  3. Choose your source language

  4. Upload your localization files or start adding keys manually

  5. Invite team members and begin translating

For detailed guidance, see our Creating Your First Project guide.

What file formats are supported?

Localit.io supports all major localization formats:

  • JSON (.json)

  • Android XML (.xml)

  • iOS Strings (.strings, .stringsdict)

  • Gettext (.po, .pot, .mo)

  • Subtitles (.srt)

Additional formats like .xlf, .properties, .resx, .csv, .yml are coming soon.

For detailed information about each format, see our File Formats Overview and specific guides:

Is there a free plan available?

Yes, Localit.io offers a free plan that includes basic features for small projects. You can upgrade to paid plans as your project grows and you need more advanced features.

File Management

How do I upload translation files?

  1. Go to your project dashboard

  2. Click "Upload Files" or use drag-and-drop

  3. Select the file format and configure import settings

  4. Choose target language for each file

  5. Click "Upload" to process the files

For detailed upload configuration options, see our File Upload Settings Configuration guide.

Can I export my translations in different formats?

Yes! Localit.io supports universal placeholders, which means you can:

  • Upload files in any supported format

  • Translate once

  • Export to multiple formats (JSON, XML, .strings, etc.)

  • Automatically convert placeholders to match target platform

What are universal placeholders?

Universal placeholders allow you to work with one set of translations for all platforms. Instead of maintaining separate translations for web, iOS, and Android, you translate once and Localit.io automatically converts placeholders during export.

Example:

  • Source: "Hello, [%s:username]! You have [%d:count] messages."

  • Web export: "Hello, {{username}}! You have {{count}} messages."

  • iOS export: "Hello, %@! You have %li messages."

  • Android export: "Hello, %s! You have %d messages."

For comprehensive information, see our Universal Placeholders guide and Universal Placeholders in Translation Editor tutorial.

Translation Features

What are plural forms and how do they work?

Plural forms handle different language rules for quantities. For example:

  • English: 1 item, 2 items (2 forms)

  • Russian: 1 файл, 2 файла, 5 файлов, 1.5 файла (4 forms)

  • Polish: 1 plik, 2 pliki, 5 plików, 1.5 pliku (4 forms)

Localit.io automatically detects and manages the correct number of plural forms for each language.

For detailed information, see our Working with Plural Forms guide and Plurals and Arrays in Translation Editor tutorial.

Can I use automatic translation services?

Yes, Localit.io integrates with multiple AI translation services:

  • Google Translate - for basic translations

  • DeepL - for higher quality translations

  • ChatGPT - for context-aware translations

  • Gengo - for professional human translators

How do I work with arrays in translations?

Arrays allow you to manage lists of related translations (like menu items). When creating a key:

  1. Select "Array" type

  2. Add elements with indices [0], [1], [2], etc.

  3. Translate each element separately

  4. Export maintains array structure for your platform

Team Collaboration

How do I invite team members?

  1. Go to Project Settings → Team

  2. Click "Invite Member"

  3. Enter email address and select role:

    • Admin - full project access

    • Translator - can translate and review

    • Developer - can manage keys and integrations

  4. Send invitation

For complete team setup guidance, see our Setting Up Your Team guide.

What collaboration features are available?

  • Comments - discuss specific translations

  • Built-in chat - team communication with support for images and voice messages

  • Translation history - track all changes and contributors

  • Status tracking - monitor translation progress

  • Review workflow - quality assurance process

How does the built-in chat work?

The integrated chat system allows your team to communicate directly within the project:

  • Send text messages - real-time team communication

  • Share images - send screenshots, designs, or visual references

  • Voice messages - record and send voice notes for complex explanations

  • File sharing - attach documents and resources

  • Project context - all conversations stay within the relevant project

How do I manage multiple teams and projects?

Localit.io supports multiple teams and projects:

  1. Create teams - organize different groups for different projects

  2. Switch between teams - easily toggle between different team workspaces

  3. Team-specific projects - each team can have its own set of projects

  4. Role management - assign different roles per team

  5. Isolated workflows - keep different teams' work separate

Example use cases:

  • Company teams - separate teams for different product lines

  • Client work - different teams for different clients

  • Project types - mobile app team vs. web development team

Can I work offline?

Localit.io is a web-based platform that requires internet connection. However, you can:

  • Export files to work locally

  • Import updated translations when back online

  • Use mobile version for translations on the go

Integrations

Which version control systems are supported?

Currently supported:

  • GitHub (including GitHub Enterprise)

  • GitLab (including self-hosted)

  • Bitbucket (including Bitbucket Server)

All major version control platforms are now supported with full integration capabilities.

How does GitHub/GitLab/Bitbucket integration work?

Integration allows automatic synchronization:

  1. Pull - import translation files from repository to Localit.io

  2. Push - export translations from Localit.io to repository

  3. Webhooks - automatic updates when repository changes

  4. Branch management - work with specific branches

All three platforms support the same core functionality with platform-specific configuration options.

For detailed setup instructions, see our integration guides:

Do I need special permissions for integrations?

Yes, you'll need to create access tokens with appropriate permissions:

  • GitHub: Fine-grained tokens with Contents, Metadata, Pull requests, and Webhooks permissions

  • GitLab: Project Access Token with api, read_repository, write_repository, and read_api scopes

  • Bitbucket: App passwords or Repository access tokens with repository read/write and webhook permissions

Technical Questions

How are placeholders displayed in the editor?

Placeholders appear as numbered blue circles (①②③) in the translation interface for better readability. You can:

  • Click circles to insert placeholders automatically

  • Toggle code view to see actual placeholder syntax

  • System tracks which placeholders are missing from translations

What happens if I don't use all placeholders in translation?

The system automatically warns you about:

  • Missing placeholders in translations

  • Shows unused placeholders below the translation field

  • Prevents saving incomplete translations

Can I customize plural rules for languages?

Yes, you can configure plural rules in Project Settings → Languages. This allows you to:

  • Override default language plural forms

  • Add custom plural forms for specific use cases

  • Match your application's specific requirements

File Import/Export

What import options are available?

Key import settings include:

  • Replace changed translations - update existing keys

  • Fill empty keys with key name - for placeholder translations

  • Convert to universal placeholders - standardize placeholder format

  • Plural format configuration - handle plural forms correctly

For comprehensive import configuration details, see our File Upload Settings Configuration guide.

What export options can I configure?

Export settings include:

  • Placeholder format - choose target platform format

  • Plural format - for JSON files

  • Fallback language - substitute missing translations

  • Key sorting - organize file structure

  • File naming - custom folder and file names

For detailed export configuration options, see our File Download Settings Configuration guide.

How do I handle large projects?

For large projects:

  • Use platform-specific filtering during export

  • Organize keys with consistent naming conventions

  • Use status filters to export only completed translations

  • Consider breaking large projects into smaller modules

Troubleshooting

My files won't upload. What should I check?

Common upload issues:

  1. File format - ensure correct format selection

  2. File encoding - use UTF-8 for international characters

  3. File size - check if within limits

  4. Syntax errors - validate file structure before upload

Translations aren't syncing with my repository

Check these items:

  1. Token permissions - ensure all required scopes are enabled

  2. Repository access - verify token has access to target repository

  3. Branch existence - confirm specified branch exists

  4. File paths - check file locations match configuration

Some placeholder formats aren't converting correctly

Placeholder conversion issues:

  1. Enable conversion - turn on "Convert to universal placeholders" during import

  2. Manual correction - some complex placeholders may need manual adjustment

  3. Format compatibility - ensure target format supports your placeholder types

AI translations marked as "Needs Attention"

This happens when:

  • Source language lacks plural forms that target language requires

  • Missing forms get translated as "Many" form

  • Review and manually correct these translations

  • Test with different quantity values (0, 1, 2, 5, 11, 21)

Best Practices

How should I organize my translation keys?

Good naming conventions:

  • Use descriptive, hierarchical names: navigation.home, buttons.save

  • Avoid generic names: text1, label, message

  • Group related keys: errors.network, errors.validation

  • Be consistent across your project

What's the recommended workflow for new projects?

  1. Plan structure - design your localization file organization

  2. Create empty files - set up basic file structure in your repository

  3. Set up integration - connect Localit.io to your repository

  4. Import structure - pull files to establish key structure

  5. Translate content - use editor or order AI translations

  6. Review quality - check translations before deployment

  7. Push to repository - update your codebase with translations

For a comprehensive workflow guide, see our Basic Localization Workflow tutorial.

How can I ensure translation quality?

Quality assurance tips:

  • Use comments - provide context for translators

  • Review workflow - implement approval process

  • Test with real data - use actual values in placeholders

  • Check plural forms - test with various quantities

  • Maintain glossaries - ensure consistent terminology

Support

How can I get help if I'm stuck?

  • Documentation - comprehensive guides for all features

  • In-app chat - contact support directly from the platform

  • Community - connect with other users

  • Direct contact - reach us via WhatsApp and Telegram

Can I migrate from other TMS platforms?

Yes, Localit.io supports migration from other translation management systems. Export your data from the current platform and use our import features to transfer:

  • Translation keys and content

  • Team structure and permissions

  • Project organization

How do I report bugs or request features?

  • Use the feedback system in the application

  • Contact support through in-app chat

  • Reach out directly via our communication channels

  • Provide detailed information about the issue or feature request