Bulk-upload PO translation files from a GitHub repo to translate.wordpress.org
Users
4
0 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#274K
#228K among extensions
Version
1.0.3
updated 5 Jun 2026
Users
monthly, 4 months
Latest, 16 Oct 2026:4 usersMove the mouse over the chart for any month
Ratings count
monthly, 4 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About GlotPress Bulk Uploader
If you maintain a WordPress plugin or theme that is translated into many
languages on translate.wordpress.org, you already know the tedious part:
uploading PO files one locale at a time, through the GlotPress import form,
again and again. GlotPress Bulk Uploader was built to remove exactly that
grind.
Why it exists:
This extension grew out of a very real workflow. A lot of plugin and theme
authors keep their translations out of the shipped ZIP and rely entirely on
translate.wordpress.org. Every time the strings change, you are left with a
folder full of PO files, one per locale, that all need to land on GlotPress.
Doing that by hand means opening the import page, choosing the plugin, the
sub-project and the locale, picking the file, submitting, then repeating the
whole thing dozens of times. It is slow, easy to get wrong, and genuinely
discouraging when you support 40 or 50 languages. The single goal of this tool
is to turn all of that into one click.
What it does:
Point it at a folder of .po files in a GitHub repository and it uploads them in
bulk to the matching plugin project on translate.wordpress.org. It maps each
file to the correct sub-project (for example stable or stable-readme) and to the
right locale automatically, and shows you the progress live as it goes.
How it works, step by step:
1. Source. You choose a GitHub repository, a branch and the folder that holds
your PO files. The extension reads the file list directly from GitHub using
the session you are already logged into, so there is nothing to download or
drag around by hand.
2. Detect and select. It parses the file names, works out the locale and
sub-project for each one, and presents them as a checklist. You stay in
control: untick anything you do not want to send.
3. Target. You pick the destination plugin (loaded from the list tied to your
WordPress.org account) and the import status: "waiting" to submit for review,
or "current" to approve directly if you have editor rights (PTE/GTE).
4. Upload and watch. The extension submits each file to the GlotPress import
form, one after another, and reports every result live in the log panel:
each success, each failure with the exact reason, and a final summary. When a
locale fails you see why (missing import permission, locale not present on
GlotPress, and so on) instead of a silent error.
Why there are no tokens and no backend:
This is a deliberate design choice. translate.wordpress.org does not offer a
convenient import API, so the obvious alternative would be a service that stores
your credentials and uploads on your behalf. We did not want that. Instead, the
extension reuses the sessions you already have open in your own browser on
github.com and translate.wordpress.org. Nothing is sent to us or to any third
party, there is nothing to configure, and there are no credentials sitting on
someone else's server. It is the most private way to do this, and it happens to
be the simplest too: install it and use it.
Who it is for:
Plugin and theme authors, translation editors (PTE/GTE) and teams who manage
many locales on translate.wordpress.org and are tired of the
one-file-at-a-time import screen.
Requirements:
- An active github.com login with access to the repository that holds the PO
files.
- An active translate.wordpress.org login with permission to import
translations for the chosen plugin.