Display your translation progress, right in your README.

Connect your Crowdin project once. Get two images — translation progress and top contributors — that stay live and update themselves, with nothing to rebuild or maintain.

What appears in your README

Translation progress table showing French 96%, German 88%, Spanish 82%, Japanese 67%, Portuguese 54%, and Korean 31% complete Grid of contributor avatars including Amara Okafor, Kenji Watanabe, Lucia Fernandez, Piotr Nowak, Hana Kim, Diego Alvarez, Elin Svensson, Raj Patel, and Noor Hassan Overall translation progress bar showing 69% complete, 3,554 of 5,100 words translated Circular progress badge showing 69% overall translation completion

How it works

  1. Create a Crowdin token

    Our setup guide walks you through it — just a few scopes, nothing your project doesn't need.

  2. Paste it in

    It's encrypted the moment we receive it, and never stored anywhere in plain text.

  3. Add the images to your README

    From there they take care of themselves — nothing to rebuild, run, or remember.

Build your own

Pick an image type, tweak the colors, and copy the URL. Everything here is just a query string — no re-onboarding required to change it later. This preview uses sample data; once you're set up, swap {public_id} for your real one.

Preview of your chosen settings

{public_id} is a stand-in — set up your project to get a URL that actually works.

FAQ

How do I revoke access?

Use the revoke link you were given when you ran setup — it's shown once, right after your embed URLs, so save it somewhere at the time. Opening it and confirming immediately and permanently disables that project's embed images, no waiting required. Deleting the Personal Access Token in your Crowdin account works too, and even faster (it takes effect before our cache expires), but doesn't remove the project record itself the way the revoke link does. A lost revoke link can't be recovered — deleting the Crowdin token is what actually matters, since it cuts off access immediately and leaves the leftover database row encrypted and useless.

What can the token you're storing actually do?

If you set it up the way our guide recommends (Projects and Translation status as Read only, Reports as Read and Write, since Crowdin requires Write access just to generate a report even though nothing actually changes), then a worst case scenario, whether that's our database being compromised or a token being intercepted mid-use, only exposes read access to translation progress and contributor activity on that one project. It can't touch translations, invite anyone, or reach any other project on your account. That said, we can't enforce those scopes on Crowdin's side. If you paste in a token with broader access, it'll still work, it's just on you to know that widens the risk.

What happens if I delete my Crowdin token but don't revoke here?

Nothing dramatic. On the next cache refresh Crowdin will start returning an error, and your image will keep showing its last known state until that stops working too, at which point it just goes stale. Your project stays in our database, encrypted and useless without a valid token, until you use your revoke link to remove it. It doesn't quietly expire on its own — see the previous question if that link is lost.

Can you read my Crowdin data?

Only what your token allows us to see: translation progress and top contributor stats for the one project you registered. Your Crowdin Project ID is stored as plain text, since it isn't a credential on its own, though that's worth knowing if your project happens to be private. See our Privacy Policy for the full details.

Is this affiliated with Crowdin?

No. This is an independent, unofficial project built on top of Crowdin's public API using their official Go client.

What if I change my mind about a limit or unit value?

Just change the query string in your README. There's nothing to set up again since your public_id stays the same either way.

Where's the source code?

Right here on GitHub. For a tool that asks you for an API token, being able to read the actual code counts for a lot more than anything we could write on this page.