Add your POT file
Drop one or more .pot files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
POT to STRINGS
Converting a .pot font to .strings repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
Private for supported formats — processed in your browser
Runs on your deviceConvert supported files
Drop POT files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting GNU gettext template to Apple strings localization
Converting a .pot font to .strings repackages the same glyphs and metrics for a different delivery target. A .pot file is a gettext Portable Object Template: the same grammar as a .po file, but with every msgstr deliberately empty. It is the extraction output — the list of every translatable string found in a codebase — from which each language's .po file is created and later merged.
A .strings file is Apple's localization resource: a flat list of "key" = "value"; statements, one per translatable string, usually named Localizable.strings and stored inside a per-language .lproj directory. It is what NSLocalizedString and its SwiftUI equivalents look up at runtime. For this route the practical draw is trivially simple grammar that any tool can read or write and native to Apple's toolchain with no build step beyond copying — balanced against no plural support at all — that requires a second file in a different format, which is worth knowing before you commit a large batch.
Why convert POT to STRINGS?
The practical trigger for this conversion is usually a mismatch: with .pot, contains no translations, so it is easy to mistake an empty catalog for a broken one. Switching to .strings buys you trivially simple grammar that any tool can read or write, which is why it is the better fit for localising an existing iOS, iPadOS or macOS application. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
POT vs STRINGS at a glance
| Aspect | GNU gettext template (.pot) | Apple strings localization (.strings) |
|---|---|---|
| Format type | Text-based — characters and structure, so there is no visual quality loss | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | syntactically identical to .po; the difference is semantic — msgstr values are empty by definition | each entry is `"key" = "value";` — the trailing semicolon is required, and both sides use C-style escapes |
| Strongest at | handing a complete string inventory to translators or a translation vendor | localising an existing iOS, iPadOS or macOS application |
| Weak spot | contains no translations, so it is easy to mistake an empty catalog for a broken one | no plural support at all — that requires a second file in a different format |
| Metadata | identifiers, source strings and context survive. Empty targets are preserved as empty rather than being filled from the source. Header placeholders and source references are not carried into formats with no equivalent field | keys and translated values are preserved. Comments are not treated as structured notes, and plural rules cannot be represented — a catalog with plurals converted into .strings will lose the plural forms because the format has no way to hold them |
Pick STRINGS as the output
Select .strings in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if STRINGS is selectable, the route is real and validated.
Convert on your device
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Verify and download
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid STRINGS file. Outputs keep the original filename with the .strings extension.
POT to STRINGS questions, answered
Will converting POT to STRINGS lose quality?
There is no visual quality to lose — pot is text-oriented and strings is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Is it private to convert POT files here?
Yes — the .pot file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Where will the STRINGS file work?
Xcode reads and writes .strings natively, and every translation platform supports it because iOS work demands it. Outside Apple's ecosystem support is incidental. Novus Convert parses the quoted key/value grammar locally, tolerating the comment form, and converts to and from the other localization formats.
Will the STRINGS file be bigger or smaller than my POT?
It depends on the content: each entry is `"key" = "value";` — the trailing semicolon is required, and both sides use C-style escapes. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my POT file?
In .pot, identifiers, source strings and context survive. Empty targets are preserved as empty rather than being filled from the source. Header placeholders and source references are not carried into formats with no equivalent field. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub — check the exported file if you specifically need tags preserved.
Can I convert STRINGS back to POT?
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .pot → .strings → .pot is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.