How do I make a GitHub stats card?

Type a GitHub username and the tool pulls that account's public data live from GitHub, then draws the contribution heatmap and the key numbers into a card you can preview and download as a PNG. There's no signup and no token to paste.

Where does the data come from?

It comes straight from GitHub's public API and a public contributions endpoint, in your browser. Only public data is used, the same numbers anyone sees on the profile page, so there's nothing to authorize and no token to hand over.

Can I put the stats card in my README?

Yes. Download the PNG and commit it to your repo for a static badge. For a version that refreshes on its own, you'd generate the card from the imejis image API in your own script or scheduled job, since a README shows a saved image rather than a live page.

Why won't a username load?

Either the username is misspelled, the account is private or brand new, or GitHub is rate-limiting anonymous requests for a minute. GitHub allows a limited number of unauthenticated calls per hour, so if you generate a lot of cards quickly, wait a moment and try again.

Can I generate stats cards automatically via an API?

Yes. The card is a design made from a calendar-heatmap component and metric components. Mark those dynamic, then POST fresh numbers to one Imejis endpoint to render an updated card image on every call, perfect for a badge that updates daily.

Is the GitHub stats card generator free?

Yes, it's completely free in the browser with no signup and no watermark, and PNG downloads are unlimited. The matching image API has a permanent free tier of 100 calls per month.

GitHub Stats Card Generator

Type any GitHub username and get a live stats card, the full contribution heatmap plus contributions, repos, active days, and followers. Download a PNG for your README or profile. No signup, no token, no watermark.

Theme

Layout

Six built-in themes

Match your profile or your terminal. Pick a theme and the whole card, heatmap included, recolors instantly, then download it as a crisp PNG.

GitHub stats card in the GitHub Dark theme, with contribution heatmap and metrics — GitHub Dark

GitHub stats card in the GitHub Light theme, with contribution heatmap and metrics — GitHub Light

GitHub stats card in the Dracula theme, with contribution heatmap and metrics — Dracula

GitHub stats card in the Tokyo Night theme, with contribution heatmap and metrics — Tokyo Night

GitHub stats card in the Gruvbox theme, with contribution heatmap and metrics — Gruvbox

GitHub stats card in the Sunset theme, with contribution heatmap and metrics — Sunset

What is a GitHub stats card?

A GitHub stats card is a single image that sums up a developer's public activity. It pairs the year-long contribution heatmap, the green grid you see on a profile, with headline numbers like total contributions, public repos, active days, and followers. It's the fastest way to show what you've been building without sending someone to your profile page, which is why it's a staple at the top of README files and portfolios.

How to make a GitHub stats card

1Type a username. Enter any public GitHub username. The tool fetches that account's public data live, no login and no token to paste.
2Watch the card build. The contribution heatmap and the headline numbers draw into a card in real time, exactly as they'll export.
3Download the PNG. Click download for a high-resolution image, ready for a README, a portfolio, or a post. No watermark and no signup.
4Keep it fresh via API (optional). Save the card as an Imejis template, mark its heatmap and metrics dynamic, and POST new numbers to render an updated card on a schedule.

What can you use it for?

A living stats badge at the top of your GitHub profile README
A developer portfolio or personal site header
A "year in review" contribution recap to share
Team or open-source maintainer activity snapshots
A daily-updating card driven by the API

Built from real chart components

This isn't a one-off template. The card is a normal Imejis design made from a calendar-heatmap component and four metric components. That's the difference from a static badge service: you can open the same design in the editor, restyle it, swap the data, or drive it from the API to render a fresh card on every call. See all 24 chart and data components you can compose the same way.

Automate it with the image API

Drop the PNG in your repo for a static badge, or rebuild the card programmatically. It's a design made of a calendar-heatmap and metric components, so you can POST fresh numbers to the imejis render API and get a new image on every call, straight from your own script or cron job.

See the image API