Dark desktops
Midnight and Forest keep the surrounding surface subdued while bright activity levels remain visible.
Personal desktop background
Turn a public GitHub contribution calendar into a sharp 3840 × 2160 desktop wallpaper. Choose a palette, preview the composition, and export a PNG made in your browser.
Live canvas preview
Public contribution data is requested from a community-maintained endpoint. Its availability can vary, and it may not reflect private activity. View endpoint information
A personal activity visual
A GitHub contribution graph wallpaper turns the familiar activity calendar into a background for a laptop or desktop monitor. This maker uses the public contribution calendar associated with a GitHub username, then draws the dates, activity levels, and a concise summary into a 4K canvas. You can compare several palettes before saving a PNG at 3840 × 2160 pixels. The result is a desktop image, not a live widget: it will stay as it was when you downloaded it until you create a newer export.
The first preview is a clearly labeled sample layout. Select Load public activity to replace that sample with the selected profile's available calendar. The GitHub contribution graph wallpaper is rendered in the browser and is not uploaded to this site. The username is sent to a community-maintained public data endpoint so it can return the calendar. No password, personal access token, or GitHub sign-in is requested. If the endpoint cannot return valid data, the page keeps the error visible and does not present the sample as a successful live result.
The tool follows a short path from a public username to a downloadable image. It retrieves dated contribution counts, checks that the response contains usable dates, maps each day to one of the graph's activity levels, and paints the calendar onto a wide canvas. The PNG export has fixed dimensions, so it remains sharp on a 4K screen and can also be cropped for other desktop sizes. The page does not query private repositories or show repository names.
The browser requests data only after submission. On success, it replaces the sample, reports the date count and visible contributions, and enables download. The source graph defines activity; this tool cannot recalculate GitHub rules, repair missing days, or infer work absent from the public calendar.
The palette changes both the wallpaper background and the four contribution intensity steps. Midnight keeps a dark green base and a warm highlight; Paper uses a light surface for bright rooms; Forest and Ocean keep lower contrast around the grid; Sunset adds a warmer accent. These choices affect presentation only. They do not change dates, counts, activity levels, or the profile data returned by the provider.
Keep the calendar readable behind desktop icons: squares have consistent gaps, month labels sit above the grid, and the total stays separate. Check the image at normal scale before setting it as a background. If shortcuts cover the left edge, adjust the operating system's crop or fit setting.
Midnight and Forest keep the surrounding surface subdued while bright activity levels remain visible.
Paper uses a pale background and darker cells, which can suit a bright workspace or printed preview.
Ocean pairs blue-green activity shades with a warm accent so labels do not disappear into the background.
Sunset adds a restrained coral range. It is a styling choice, not a score or a measure of productivity.
The exported canvas is 3840 × 2160 pixels, the common UHD 4K frame for a 16:9 display. A larger source gives the operating system room to scale down on many 1080p and 1440p screens. It does not add detail to the contribution calendar; it draws squares and text at a size that avoids a blurry screenshot. Creating a PNG can use extra memory on a phone or older laptop.
The preview is scaled to fit the page; the downloaded file keeps the full dimensions. Check its properties if it looks soft. The tool does not compress a second copy or guarantee that each operating system uses the same crop.
This generator is for public GitHub profiles. It sends the submitted username to the community-maintained endpoint below and receives a visible calendar as JSON. It has no credential field: do not enter passwords, tokens, email addresses, or private values. The calendar may include an anonymized activity signal when the profile owner enables that setting, but it does not expose private repository names.
The endpoint is a third-party service rather than an official GitHub API. Its response can be delayed, rate limited, incomplete, or temporarily unavailable. Treat the generated wallpaper as a visual copy of the data returned at that moment, not as an official record or proof of work. If an activity day is absent, first compare the profile's contribution calendar and GitHub's own contribution rules. A wallpaper generator cannot correct commit email, branch, fork, private-visibility, or timezone issues. The downloaded image is static and can become outdated as new activity appears.
A desktop background can hold a personal activity visual without replacing project evidence. The grid shows a rhythm across the chosen period; the total summarizes public data. It is not a productivity grade or proof of work. Contribution events do not explain their context or quality.
A 4K wallpaper is not optimized for a narrow README or a frequently updated page. Use a live image when freshness matters. Our contribution PNG guide covers static publishing; the graph rules guide explains missing activity.
If the username is rejected before a request begins, check that it contains only a GitHub-style profile name with letters, numbers, or hyphens. The form rejects spaces, a leading or trailing hyphen, and credential-like values. If the provider says the account cannot be found, confirm the spelling and that the profile is public. A valid username can still fail when the community endpoint is down or enforcing a temporary rate limit; wait and retry rather than submitting the form repeatedly.
If the calendar looks sparse, compare it with the profile's visible graph; the response only covers the selected period and activity the source can see. If download fails, check browser download settings. On a low-memory device, close large tabs and retry. Live totals stay hidden until a real response replaces the labeled sample.
The maker does not sign in, read private repository names, use a token, or upload the generated file. It does not fetch a profile biography, avatar, repositories, or followers. Its output is one user-selected public calendar rendered as a local PNG.
A square records activity in the upstream graph's format, not its quality or context. Check GitHub's rules when days are missing. Use GitHub City for interactive 3D exploration and the contribution PNG guide for static publishing.
Enter a public GitHub username, choose the contribution period and a palette, then load the calendar. Review the preview and download the 3840 × 2160 PNG. The first image on the page is only a labeled sample until public data loads.
Yes. The PNG canvas is 3840 × 2160 pixels in a 16:9 layout. The on-page preview is scaled to fit your browser, but the downloaded file uses the full canvas dimensions.
No. It requests the visible contribution calendar for a public username through a third-party endpoint. Do not enter passwords, personal access tokens, or private account details.
It can only show the activity signal that the upstream public calendar returns. It does not reveal private repository names or details, and it cannot access an account that requires authorization.
The username may be misspelled, the public endpoint may not find the profile, or the service may be unavailable or rate limited. Check the profile name, wait briefly, and try once more.
No. The image is a static file. Generate and download another wallpaper when you want to include later activity.
You can, but a desktop wallpaper is not optimized for a narrow README and will become stale. Use a live contribution card or workflow when the image needs to update, and add explanatory text around it.
Compare the source profile graph first. The exporter follows upstream data and cannot repair issues caused by commit email, default branch, fork rules, private-contribution settings, or update timing.