Convert iOS's .plist to Multilingual INI Instantly

Converting localization files manually is time-consuming, error-prone, and disrupts your workflow. With Localazy's Format Conversion, you can automatically transform your iOS's .plist files into Multilingual INI , eliminating manual effort and ensuring accurate results every time.

Try Localazy Now

Why Convert iOS's .plist to Multilingual INI
with Localazy?

Automate Localization Workflows

Process files in seconds instead of hours.

Seamless CI/CD Integration

Convert files automatically as part of your release cycle.

Unified File Management

Maintain a single localization source for multiple platforms.

Error-Free Transformation

No more formatting issues, broken placeholders, or missing translations.

Convert your iOS's .plist to Multilingual INI with Localazy now!

Sign up now and try it for free!

Start now

Quick comparison

Multilingual INI

File extension

Hierarchy handling

Best for

Multilingual INI

Extended INI format for localization

File extension

.ini

Hierarchy handling

Key-value with language markers

Best for

Windows multi-language support

Find more in docs

Choose the right format for your project needs
View detailed format guide

Format Conversion{{automated}}

Set up automated conversion between required formats with Localazy CLI.

Learn more

From: iOS's .plist

localazy_message = "Go international, today. With Localazy."

To: Multilingual INI

[en]
localazy_message = "Go international, today. With Localazy."
[es]
localazy_message = "Internacionalízate hoy. Con Localazy."

Supported formats & flexibility

We support XX+ localization formats, including JSON, XML, XLIFF, YAML, PO, and more.

iOS's .plist to Android XML

iOS's .plist to Flutter ARB

iOS's .plist to CSV/TSV

iOS's .plist to Multilingual CSV/TSV

iOS's .plist to Microsoft Excel

iOS's .plist to Multilingual Microsoft Excel

iOS's .plist to INI

iOS's .plist to Multilingual INI

iOS's .plist to iOS's .strings

iOS's .plist to iOS's .stringsdict

iOS's .plist to JSON

iOS's .plist to Mozilla i18n JSON

iOS's .plist to Multilingual JSON

iOS's .plist to Gettext MO

iOS's .plist to Nette Neon

iOS's .plist to Multilingual Nette Neon

iOS's .plist to OpenOffice/LibreOffice ODS

iOS's .plist to Multilingual OpenOffice/LibreOffice ODS

iOS's .plist to PHP/Laravel

iOS's .plist to Multilingual PHP/Laravel

iOS's .plist to Gettext PO/POT

iOS's .plist to RESX

iOS's .plist to Translation Memory (TMX)

iOS's .plist to TOML

iOS's .plist to Multilingual TOML

iOS's .plist to XCode Strings Catalog

iOS's .plist to XLIFF 1.2

iOS's .plist to XLIFF 2.0

iOS's .plist to YAML

iOS's .plist to Multilingual YAML

iOS's .plist to Rails i18n YAML

Documentation

Getting started with Localazy

Managing project glossary

Translating strings

Machine Translations

Format Conversions

Reviewing translations

Automations

How to convert language files

Which localizable file format conversions do you support?

Localazy supports all major format conversions from Android XML and iOS .strings through multilingual JSON to XLIFF, qt-ts, and many more formats. You can learn more about supported file format conversions in the documentation.

Last updated: 26/05/2023

How can I convert different localization file formats?

In the File Management section of Localazy, when downloading your files, you can select the desired format and download your strings in any of the available file formats.

Format Conversions feature is also an integral part of the Localazy CLI tool, so if you want to automate format conversions, you will need to install Localazy CLI on your preferred platform.

Read the article: How to convert localization files into different formats?

Note: Format Conversions are available only as a part of the Professional plan

Last updated: 26/05/2023

How can I use Format Conversions for multiplatform development?

Format Conversions in Localazy allow you to convert translation files between different formats, making it easier to manage translations across multiple platforms. For instance, if you’re developing an app for iOS and Android, you can easily convert between .strings (iOS) and .xml (Android). This eliminates the need to manually maintain translations for each platform, saving time and reducing the risk of errors.

Last updated: 30/09/2024

How are placeholders handled with Format Conversions?

Format Conversions support placeholders across various formats, but their syntax can differ between platforms. For example, in Android, placeholders are typically in the format %1$s, while in iOS, they use %@. Localazy automatically converts these placeholders to the appropriate format for the target platform, ensuring that your translations work correctly without manual adjustments.

Last updated: 30/09/2024

How are nested structures handled with Format Conversions?

Some formats, like JSON or YAML, support nested structures in translation files. Localazy’s Format Conversions preserve these nested structures during conversion. When converting from a format that supports nesting to one that does not (such as from JSON to XML), Localazy flattens the structure to ensure compatibility without losing any translation data.

Last updated: 30/09/2024

How are plurals and arrays handled with Format Conversions?

Plurals and arrays are managed differently across platforms, but Localazy automatically handles these conversions for you. For example, Android uses specific plural keys (one, other), while iOS handles plurals with string tables. Localazy’s Format Conversions ensure that plurals and arrays are correctly mapped and formatted to suit the target platform’s specifications.