SleekView for Loco Translate: PO files and strings as customizable tables
Loco Translate is a file-based PO and POT editor with no custom database tables. SleekView indexes those files and surfaces project coverage as a sortable list across every theme and plugin on the site.
♾️ Lifetime License available
PO files without the directory dive
Loco Translate is unusual in the WordPress translation ecosystem because it doesn't store translations in the database at all. Instead it edits PO and POT files in wp-content/languages, theme directories, and plugin folders. That makes it portable but turns coverage reporting into a directory-walking exercise. SleekView indexes the file footprint into one table with project, type, language, translated count, total count, and last-modified columns.
The default Loco UI groups projects by source — Author, Custom, System — and shows coverage per project on its own screen. There's no sortable cross-project view, so finding which themes and plugins are at less than 50% French coverage means clicking into each project and noting numbers. SleekView ranks every project by translated-strings ratio in one query.
For maintainers, this matters at deploy time: a site that ships with WooCommerce 8.5 needs language packs for that exact version, and a sortable list of project-version-language coverage answers the question fast. For translators picking the next project, sorting on remaining-strings-in-DE is a one-click operation instead of a hunt.
Workflow
How SleekView indexes Loco Translate files
Index PO and POT files
Rank coverage cross-project
Save coverage queues
Hand off scoped briefs
Sample columns
A typical Loco Translate PO file view
Filesystem PO/POT files (no custom database tables; Loco Translate is a file editor)
| Project | Type | Language | Strings translated | Status | Last modified |
|---|---|---|---|---|---|
| WooCommerce | Plugin | DE | 1284 / 1320 | Active | Apr 24, 2026 |
| Storefront | Theme | FR | 612 / 940 | Partial | Apr 21, 2026 |
| Yoast SEO | Plugin | FR | 0 / 1880 | Missing | n/a |
| Twenty Twenty-Four | Theme | DE | 182 / 182 | Active | Apr 18, 2026 |
Comparison
Default Loco Translate admin vs SleekView
Default Loco Translate admin
- Project list is grouped by source rather than searchable as a whole
- Coverage numbers are visible per project, not in a sortable column
- No saved filters across themes and plugins
- Bulk audits across many plugins require many clicks
- Last-modified columns are not exposed in one place
SleekView
- All Loco projects in one sortable table
- Saved views for missing or partial coverage
- Filter by language, project type, or last modified
- Translated count column with sort
- CSV export for translator handoffs
Features
What SleekView gives you for Loco Translate
Themes and plugins together
Every PO file Loco Translate has indexed shows up in one table with project type, language, translated count, and last-modified columns sortable in any direction.
Spot coverage gaps
Sort by translated-strings ratio or filter to missing-in-French projects to find where the next translation hour pays off most across the whole site.
Quick metadata edits
Inline-edit project notes and tags. PO file string content still opens in the Loco editor, where the in-context UI is a better fit for the actual translation work.
Audience
Who uses SleekView for Loco Translate
Localization managers
Audit which themes and plugins have full or partial coverage in each language and prioritise the highest-traffic gaps before the next deploy.
Translators
Pick the next project to work on by sorting on remaining strings per language, instead of clicking into every project to find the largest backlog.
Maintainers
Confirm shipped language packs match the deployed theme and plugin versions, so customers don't see English mid-flow on a German site.
The bigger picture
Why file-based translation needs a sortable index
Loco Translate's file-based design is a strength for backups, version control, and multilingual deployments. It's also the reason cross-project audits are slow. The default admin gives a per-project view but no sortable list, so the answer to which-language-packs-need-work-before-Friday's-deploy is gathered by clicking through twelve theme and plugin entries and writing numbers in a notebook.
That works once. By the third Friday it's unsustainable. Indexing the PO files into one sortable table changes the rhythm.
A localization manager picks the highest-leverage gaps — WooCommerce missing 600 strings in French, Storefront at 65% in Spanish, Yoast SEO not started in Italian — and assigns work in a single sitting. Maintainers pre-empt the support tickets that appear when a customer's checkout flips to English mid-flow because the WooCommerce language pack drifted. The string editing still happens inside the Loco editor, where the in-context UI helps.
The audit and prioritisation move to a place where they can be done at speed.
Questions
Common questions about SleekView for Loco Translate
On the filesystem, in PO and POT files inside theme, plugin, and language directories. There are no custom database tables, which makes Loco's translations portable across deployments but means cross-project reporting requires indexing the files. SleekView does that indexing in WP admin only.
Editing actual translation strings still happens inside the Loco editor, where the in-context UI is the right fit for that work. SleekView surfaces project metadata, coverage ratios, and last-modified timestamps so the audit and prioritisation work happens at speed.
Yes. Filter and sort across every Loco project by language, project type, translated-strings ratio, or last-modified. The filter combination saves as a view, so a Friday-deploy audit reloads the same scoped list each week.
Yes. SleekView indexes both, with a column showing project type. Custom Loco projects — author-defined paths outside the standard theme and plugin directories — also surface, so all language work is visible from one screen.
Yes. Any saved view exports to CSV with project, file path, language, translated count, and total count columns. Translators and maintainers receive a scoped brief that maps directly to the PO files needing attention.
No. SleekView indexes PO file metadata in WP admin only and paginates server-side. The front-end gettext lookups that load translations on every page render run unchanged, since they read compiled MO files separately.
Yes. If you have configured a custom project in Loco — for example, translations stored under a custom plugin or mu-plugin path — SleekView includes it in the index alongside theme and plugin projects, with the same coverage columns.
Yes. SleekView surfaces both PO and MO last-modified timestamps, so it's clear when a PO was edited but the compiled MO hasn't been regenerated yet — a common cause of translations that look right in Loco but don't render on the front end.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout