# Free GitHub Wrapped Generator

> Free GitHub Wrapped: enter a username and get five story cards for a year: repos, stars, languages, rhythm and busiest repo.

Source: https://gitwow.org/github-wrapped | Updated: 2026-11-21

## Key takeaways

- Five cards cover a year: intro, building, languages, rhythm and busiest repository, drawn in your browser from public data.
- Repository cards use the whole year. Rhythm and Busiest use public events from a short recent window, and the dates under the cards show the range.
- Private work and commit counts are not shown, and the tool asks for no sign-in and no token.
- The cards download as one PNG or as separate SVG files, and the page address holds the username and the year.

Type a username and a year, and the page draws five story cards from that profile's public data: repositories, stars and forks, languages, your weekly rhythm and your busiest repository. Each card counts one thing you can check on GitHub yourself. Plain version: it is a year in review made of facts, ready to download as images.

## Each of the five cards counts one thing you can check

| Card | What it shows | Where it comes from |
| --- | --- | --- |
| Intro | The year, your name, followers and public repositories | The profile, as it is today |
| Building | Repositories created that year, repositories pushed to, and the stars and forks of the ones created that year | The repository list |
| Languages | Top five languages by number of repositories pushed to that year | The repository list |
| Rhythm | Most active weekday, usual hour, longest run of active days and the number of active days | Public events |
| Busiest | The repository with the most public events, and how many | Public events |

The repository list is read in up to two pages of 100, newest push first, with forks left out. The events are the public events feed for the account, read in up to three pages of 100.

## Maintainers, learners and DevRel teams post the cards for different reasons

- A maintainer posts the Busiest card to show which project took the year.
- A junior developer with a portfolio posts the Languages card to show what they actually build in.
- A course author asks students to share their cards at the end of a term.
- A DevRel team collects the cards of its speakers for a year-end recap page.

## Three steps take a username and a year to five images

1. **Choose an account and a year.** Paste a username or a profile link and pick the year from the list, which holds the current year and the four before it.

![Free GitHub Wrapped with a username and a year selected](https://gitwow.org/img/content/tools/github-wrapped-step-1.webp)Step 1: a username and a year are the two inputs.

**Swipe through the cards.** They sit in a row you scroll sideways. A line under them prints the first and last date of the events the Rhythm and Busiest cards used, so you can see the window they cover.

![Five story cards in a row: intro, building, languages, rhythm and busiest](https://gitwow.org/img/content/tools/github-wrapped-step-2.webp)Step 2: five cards, with the covered dates printed underneath.

**Download, copy or embed.** "Download all as PNG" saves the five cards side by side in one file, each card also has its own SVG button, and "Copy link" saves an address that holds the username and the year. The Embed window gives the iframe code for the page as it is now.

![Embed window with theme, accent, background, corners and height settings and iframe code](https://gitwow.org/img/content/tools/github-wrapped-step-3.webp)Step 3: the Embed window carries the username and the year.

## The cards read public events from a short recent window, and they say so

The Rhythm and Busiest cards depend on the account's public events. The tool states on screen that GitHub keeps only the last 90 days of them, and it reads at most three pages of 100, so 300 events is its ceiling. On a busy account the covered window can end up shorter than 90 days. The dates printed under the cards show the real range, so rely on them for the exact span.

The cards also leave out:

- Private work. Only public repositories and public events are read.
- Commit counts. Public events do not carry them, so the tool does not show a number it cannot back up.
- Anything that needs GitHub sign-in or a token. The tool asks for neither.

When a card has no data, it says "Nothing to show" and names the reason. Rhythm and Busiest turn up empty for any account with no public events in the window.

## Four details decide how to read each number

- Stars and forks on the Building card are the totals today, on repositories created in the chosen year. They are not stars earned during that year.
- Languages count repositories, not lines of code, and each repository contributes the one language GitHub lists for it.
- A repository counts as pushed to in a year by its last push date. A project you kept working on later shows up under the later year.
- Weekday and hour use the time zone of the browser that opens the page, and the streak counts days in a row with at least one public event inside the window.

When an account has more public repositories than were read, a status line says how many of the total came from the most recent pushes.

## Past years keep the repository cards and lose the rhythm

For a past year the Intro, Building and Languages cards use the whole year, because they come from the repository list. Rhythm and Busiest need events from that year, and the window above rarely reaches back that far, so they stay empty or cover only part of it. The page shows a notice that says this. For the full rhythm of a year, run the page for the current year while it is current and save the PNG.

## Post the cards yourself, with one fact from them in the caption

A card with a fact you can verify, such as your busiest repository or your most active weekday, gives a caption something specific to say. Write the caption yourself in a sentence or two and post the PNG where your developer network reads. If you want more people to see the post, [free GitHub followers](https://gitwow.org/get-free-github-followers) brings developers to your profile, and [free GitHub stars](https://gitwow.org/) helps the repository that took your year get noticed.

To see what else a profile shows, [the profile analyzer](https://gitwow.org/github-profile-analyzer) scores twelve checks, and [the worth calculator](https://gitwow.org/github-worth-calculator) gives an impact score and an estimated reach. [The star history chart](https://gitwow.org/github-star-history) follows a repository's stars over time. For the green contribution grid and private contributions, see [our article on the contribution graph](https://gitwow.org/blog/github-contribution-graph). To put live numbers in your README, use [the stats card generator](https://gitwow.org/github-readme-stats-generator) or [the profile README generator](https://gitwow.org/github-profile-readme-generator).

## Embed the cards or give an agent the address

The Embed button beside the title opens a window with theme (dark or light), accent color, background, corner radius and height, plus a live preview and the iframe code. The embed is at /embed/github-wrapped, and [this example link](https://gitwow.org/embed/github-wrapped?user=torvalds&year=2025&theme=light) opens the 2025 cards for torvalds in a light theme. The parameters are user and year, and all tools are listed in [/llms.txt](https://gitwow.org/llms.txt), so an agent can open a link and read the result.

## What is different here

- Free, with no sign-in to GitHub, and no token.
- The limits of the data are on this page and printed on the result.
- Five cards, drawn in your browser, which open quickly and download as images.
- Facts about your year, with no joke labels to guess at.
- The card set is a link, an embed or an address an agent can read.

## Frequently asked questions

### What is GitHub Wrapped?

It is a year in review for a GitHub profile, in the style of Spotify Wrapped. Our version has five cards: intro, building, languages, rhythm and busiest repository. Each card counts something you can check on GitHub.

### How do I get my GitHub Wrapped?

Enter your username, pick the year and press the button. The cards are drawn in your browser from public data, and the address then holds your username and year so you can share it.

### Does it include private contributions?

No. Only public repositories and public events are read, and no sign-in or token is involved. For how GitHub's contribution grid treats private work, see our article on the contribution graph.

### Why do some cards say Nothing to show?

Rhythm and Busiest are built from public events, and the tool states that GitHub keeps only the last 90 days of them. An account with no public events in that window, or a past year, leaves those two cards empty. The dates printed under the cards show the range that was read.

### Can I get a wrapped for a past year?

Yes, from the year list, which holds the current year and the four before it. The Intro, Building and Languages cards work for any of them, and Rhythm and Busiest stay empty or partial because they need events from that year.

### How are top languages calculated?

By counting repositories. Each repository pushed to in the chosen year adds one to the language GitHub lists for it, forks are left out, and the five highest counts are shown. Lines of code are not measured.

### Is it official GitHub?

No, it is a GitWow tool. GitHub's own blog has featured a separate open-source project called GitHub Unwrapped, which gives stats and highlights on your year in code, so the idea is a familiar one.

### How do I share it?

Download all five cards as one PNG, or each card as an SVG, or copy the link. A caption with one fact from the cards, such as your busiest repository, gives the post something to say.

