Poedit
Desktop translation editor for gettext catalogs and translation files.
Open the official app on poedit.net
This tool is hosted by its maintainers. Click below to open poedit.net in a new tab — it's their official demo.
Browse writing & tools tools →What's next with Poedit?
Choose how you want to get started.
Use it free
Open the official tool or demo — no account needed.
Self-host it
Run the open-source version on your own infrastructure.
What is Poedit?
Poedit is a translation editor designed for managing localization files in formats such as PO (Portable Object), XLIFF, JSON, Qt, and Flutter. It serves as a graphical frontend for the GNU-gettext system, enabling translators and developers to efficiently handle internationalization tasks. The tool is particularly useful for projects using gettext for localization, including PHP frameworks like Drupal and WordPress, Python projects like Django, and Linux-based applications. Poedit addresses the complexity of manual translation by providing a centralized interface for editing, reviewing, and exporting translation files, reducing errors and improving workflow efficiency. Its intuitive design and safety checks make it accessible to both novice and experienced users, while its integration with cloud platforms like Crowdin and Localazy facilitates team collaboration. The tool is widely adopted by translators and developers who need to manage multilingual content across diverse software ecosystems.
How it works
Poedit is a proprietary tool that simplifies the translation of software and websites by supporting multiple localization formats. It is built to handle gettext (PO) files, which are commonly used in PHP, Python, and Linux projects, but also extends to XLIFF, JSON, Qt, and Flutter formats. The primary purpose of Poedit is to streamline the translation process by providing a unified interface for editing, managing, and exporting translation files. It helps users avoid common pitfalls like broken strings or formatting issues through built-in validation and safety checks. Poedit supports PO, XLIFF, JSON, Qt, and Flutter formats, making it versatile for projects ranging from open-source software to commercial applications. It integrates with cloud platforms like Crowdin and Localazy, allowing users to access and manage remote translation projects directly from the app. The tool also offers pre-translation features powered by machine translation engines, accelerating workflows for large-scale localization.
How to use it
- 1Download and install Poedit from its official website, available for Windows, macOS, or Linux. 2. Open the application and import your translation files (e.g.,.po,.json) or connect to a cloud project via Crowdin/Localazy. 3. Edit strings directly in the editor, using context clues and pluralization rules provided by the tool. 4. Export the translated files in the required format and verify changes using the built-in safety checks. Practical tips include leveraging cloud integration for real-time collaboration, using the 'Find and Replace' feature for repetitive phrases, and exporting files in the correct encoding format (UTF-8) to avoid corruption.
What it can do
- translation editor
Use cases
Assumptions and limitations
Assumptions
- source: https://poedit.net/
- license: Proprietary — free to use
- privacy: Opens an external demo
Limitations
- The Pro version requires a paid license, limiting free access to basic features
- Limited real-time collaboration features compared to dedicated cloud tools
- No built-in support for non-PO formats like YAML or CSV without additional plugins
- Older operating systems (e.g., Windows 7) require outdated versions with potential compatibility issues
- Manual file management is needed for complex project structures
Understanding the result
Desktop translation editor for gettext catalogs and translation files.
Tool details
- Clearly flagged when a network request is needed.
- No account, no sign-up, and no tracking of your content.
- Powered by (MIT).
- Built with
- (https://poedit.net/)
- License
- MIT
- Runs locally
- No — requires a network request
- Verification
- Not yet verified
- Input
- Query
- Output
- Text
Built with https://poedit.net/. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.
- Built with
- License
- MIT
Open-source project
OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.
References
- / — GitHub Repository
Upstream project · GitHub
- Proprietary License
Upstream project
Frequently asked
Is Poedit free to use?
Poedit offers a free version with core translation editing capabilities, but advanced features like cloud integration and machine translation require a paid Pro license. The open-source version is available under the MIT license but lacks Pro-specific functionalities.
How does Poedit handle gettext localization?
Poedit acts as a frontend for the GNU-gettext system, allowing users to edit .po files that store source and translated strings. It maintains context and pluralization rules inherent to gettext, ensuring translations align with the original software's structure and requirements.
How do I translate a WordPress theme with Poedit?
First, locate the theme's .po files in the 'languages' directory. Import these files into Poedit, edit the strings using the editor's context clues, and export the updated files. Poedit's WordPress-specific mode automates file management and ensures proper directory structure for theme activation.
How does Poedit compare to OmegaT or Lokalise?
Poedit excels in gettext-based projects and offers seamless integration with cloud platforms like Crowdin. OmegaT is more focused on CAT (computer-assisted translation) features with extensive terminology management, while Lokalise provides stronger real-time collaboration tools. Poedit's strength lies in its simplicity and compatibility with open-source ecosystems.
What should I do if Poedit can't find my translation files?
Verify that files are in the correct directory structure (e.g., 'languages/xx_XX.po') and that the file extensions match Poedit's supported formats. Check for encoding issues by ensuring files are saved as UTF-8. If using cloud integration, confirm project settings in Crowdin/Localazy match the file paths specified in Poedit.