Understanding Localization & Supported File Formats

Localization is the process of adapting software, apps, or websites to a specific language and culture. Unlike simple translation, localization includes formatting dates, currencies, UI layout adjustments, and more.

How Localization Differs from Regular Translation

Purpose of This Estimation Form

This form provides a per-string estimation for localizing your product, so you can budget efficiently before starting the full project.

Accepted File Types

We currently support the following localization file formats:

For Estimation Purposes

If you are unsure of the format, upload any text-based file with clear string structure. We will review it manually for estimation.

Examples: File Preparation by Platform

Laravel (PHP)

  • resources/lang/en/*.php – Translation files
  • resources/lang/en.json – JSON-based frontend strings

WordPress (PHP)

  • .po and .mo files – Typically located in wp-content/languages
  • Export using tools like PoEdit or Loco Translate plugin

Joomla (PHP)

  • .ini files – Located in /language/en-GB/ and extension folders
  • Example: en-GB.mod_login.ini

Django (Python)

  • .po files – Located under locale/en/LC_MESSAGES/
  • Use django-admin makemessages to extract strings

Static HTML Website

  • Manual extraction of text content from `.html` files
  • Recommended: convert to `.txt` or structured `.json` for estimation

Mobile Apps

  • Android: res/values/strings.xml
  • iOS: Localizable.strings files
  • Can be converted/exported to .xliff for bulk localization

Desktop Software

  • Depends on the framework (e.g., Qt uses .ts, .NET uses .resx)
  • Convert or export to standard formats: .po, .xliff, or .json

Unsure what to upload? You may also send a sample file or contact us. We’ll help you extract the content properly for localization.