LeetCode Stats Card

Extensions add specialized views to the card. Note: Currently, you can only use one extended-card extension at a time.

Available extensions:

• activity: Shows recent submissions.
• contest: Shows contest rating history.
• heatmap: Shows a heatmap of activity for the past 52 weeks.

Pass the extension name via the ext parameter.

# Activity extension
![](https://leetcard.jacoblin.cool/JacobLinCool?ext=activity)

# Contest extension
![](https://leetcard.jacoblin.cool/JacobLinCool?ext=contest)

# Heatmap extension
![](https://leetcard.jacoblin.cool/JacobLinCool?ext=heatmap)

To show your LeetCode stats, use a Markdown image tag pointing to the LeetCode Stats Card endpoint. Replace JacobLinCool with your LeetCode username (case-insensitive).

Standard Image:

![Leetcode Stats](httpshttps://leetcard.jacoblin.cool/JacobLinCool)

Hyperlinked Image (links to your LeetCode profile):

[![Leetcode Stats](https://leetcard.jacoblin.cool/JacobLinCool)](https://leetcode.com/JacobLinCool)

You can self-host the service using the jacoblincool/leetcode-stats-card Docker image.

To build the image manually, use the pnpm build:image script provided in the repository. An example docker-compose.yml is available in the repository root.

You can inject custom CSS into the card by providing a comma-separated list of URLs to the sheets parameter. This is useful for advanced styling. You can host your CSS on services like GitHub Gist.

![](https://leetcard.jacoblin.cool/username?sheets=url1,url2)

![](https://leetcard.jacoblin.cool/jacoblincool?sheets=https://gist.githubusercontent.com/user/style.css)

The ContestExtension is a feature of the LeetCode Stats Card that visualizes a user's contest rating history and current ranking.

Key Features

• Rating History Graph: Renders a polyline graph showing rating changes over time.
• Current Stats: Displays current contest rating, highest rating achieved, and global ranking (e.g., 123 / 50000).
• Badges: Automatically displays icons for specific LeetCode contest ranks like Guardian or Knight.
• Dynamic Scaling: The extension automatically adjusts the card height (minimum 400px) and scales the graph based on the user's rating range and time span.

Data Requirements

This extension relies on the leetcode-query library to fetch userContestRanking and userContestRankingHistory. It only plots history for contests that the user has actually attended.

The Cloudflare Worker implementation provides an endpoint to generate LeetCode stats cards as SVGs or HTML. You can request a card by providing a username as a path parameter or a query parameter.

URL Patterns

• By Username (Path): GET /<username>
• By Username (Query): GET /?username=<username>
• Demo Mode: If no username is provided, the worker returns a demo card.

Query Parameters

In addition to username, you can pass configuration options via query parameters to customize the card. One supported parameter is cache, which sets the cache-control max-age in seconds.

https://your-worker-url.com/your_leetcode_username?cache=600

You can run the LeetCode Stats Card worker using Docker Compose. The configuration defines a worker service that builds from the local directory and exposes port 8080. To persist the cache between restarts, a volume is mapped from the local ./.storage/cache directory to /worker/cache inside the container.

version: "3.8"

services:
    worker:
        build: .
        image: jacoblincool/leetcode-stats-card
        volumes:
            - ./.storage/cache:/worker/cache
        ports:
            - "8080:8080"

The cache duration is configurable via the cache parameter (in seconds).

To manually clear the cache for a specific user/site, you can make a DELETE request to the endpoint: DELETE /:site/:username.

Warning: Setting a very long cache time may result in GitHub caching the old card image instead of fetching the updated one.