Statically

statically.io ·

Statically delivers static files from public Git repositories and npm packages for free, with URLs for GitHub, GitLab, Bitbucket and Gist. Developers can reference versioned JavaScript, CSS and other assets. Files are limited to 25MB, and the former /img/ image-processing endpoint is disabled.

Git asset deliverynpm CDNFree public serviceVersioned assetsOpen-source projects
Service marketsNot verified
BillingFree public service
Free trialNot supported
Payments
Not verified
Overall rating
★★★★★★★★★★2.5

On-site interest
3,250index
01

Company introduction

About Statically
Founded
2018 (project repository origin)
Co-founders
Frans Allen (project founder)
Headquarters
Not disclosed
Listing
Developer project; not applicable

A public delivery service for open-source projects

Statically is a free CDN created by Frans Allen to deliver static files from public code repositories and npm packages for open-source projects. Its public GitHub repository was created in 2018. Resource URLs identify the repository, version and file path.

Statically is currently listed in the upset.dev portfolio of developer projects. Its official repository provides channels for reporting issues and contributing. The website names bunny.net and Cloudflare as infrastructure supporters, and the project accepts sponsorship in the form of resources and services.

Files from public repositories and npm

Statically provides URLs for serving assets from code-hosting platforms on web pages. Repository URLs identify the platform, account, repository, version and file, while GitHub Gist has its own path format. npm URLs identify a package, version and file. These links can serve website dependencies, documentation examples and static assets published by open-source projects.

Repositories must be public, individual files cannot exceed 25MB, and abuse may trigger rate limits. The service suits publicly released files. Private repository credentials, private object storage and a website’s own origin configuration require other services.

Free access and deployment choices

Public asset delivery is free, with no traffic pack or paid subscription to purchase. The project accepts voluntary Patreon sponsorship and contributions of time, resources or services from companies. These arrangements are separate from buying bandwidth, dedicated support or an enterprise availability contract. Each upstream project’s licence still applies to the files you use.

For deployment, choose a fixed commit, release or explicit npm version. Default branches and URLs that omit a version can change the dependency being delivered. Keep trusted copies and alternative paths for essential files, and check loading from the regions where your users are located.

The former image endpoint is disabled

Statically has disabled /img/ because of abuse and high traffic. Sites using those remote image-processing URLs need to migrate their calls and check existing links. The current service described here is Git and npm file delivery; the other products linked in the website footer have their own service entry points.

02

Who is this provider for?

Open-source projects publishing static assets

Deliver JavaScript, CSS and other files from a supported Git platform, with documentation or examples referencing a specific release.

Keep the repository public and each file within the size limit. Publish a new version URL for updates and check the content delivered from cache.

Frontend developers referencing npm files

Load assets by package name, pinned version and file path for demos, documentation and pages using browser-ready library builds.

Check the package contents and browser compatibility first. Delivering an npm package does not make every entry point directly usable in a browser.

Tutorial and technical-documentation teams

Create traceable references to public code examples and assets, keeping repository releases aligned with published pages.

Keep copies of essential files. Migrate old /img/ URLs separately; that endpoint no longer provides image processing.

Statically suits projects with public repositories or npm releases that want straightforward asset URLs. Sites needing continuity should manage versions, licences, integrity checks and alternative delivery paths as part of their release process.

03

Services and products

Core products from official sources

Explore products by use case: what they do, how to use them and whether they are billed separately.

Git repository and Gist file delivery

Static assets from public code-hosting platforms

Delivers files from public GitHub, GitLab and Bitbucket repositories through one CDN domain, with a separate path for GitHub Gist. Repository URLs identify the account, repository, version and file, making them useful for scripts, stylesheets and documentation assets. A repository-link converter on the website helps generate asset URLs.

Public delivery is free. Repositories must be public, the maximum file size is 25MB, and abuse may trigger rate limits.Official product information

npm package file delivery

References by package, version and file path

Retrieves files from public npm packages, with optional explicit versions and paths within the package. It suits libraries that publish browser-ready builds, as well as versioned asset references in developer tools and documentation. Check that the file exists and that its build is suitable for the intended runtime.

Included in the same free public service, with no separate API or traffic plan. File-size and anti-abuse conditions also apply.Official product information
Sources: Statically official product pages and developer documentationVerified: 2026-11-16
04

Plans and pricing

Official public pricing
Website delivery and security plans · monthly and annual billing shown separately

Public repository and npm CDN

Open-source projects distributing JavaScript, CSS and other static files from public Git repositories or npm packages.

Free

Public open-source asset delivery

  • URLs for GitHub, GitLab, Bitbucket and npm assets
  • Public repositories only; 25MB maximum per file
  • Abuse may trigger rate limits; avoid excessive automated traffic
  • Pin repository releases or commits and npm versions
  • Each upstream project’s licence still applies

Free delivery has no paid renewal cycle or traffic allowance sold by the GB. When you stop using Statically, remove or replace asset references and check that dependencies still load.

Prices checked: 2026-11-16
05

CdnChart Selection Guide

EvaluateSelection verdict

A free option for public Git and npm assets, particularly open-source documentation, demos and small static files

Before using it for a live business, assess regional reachability, dependency updates and fallback paths. Contractual guarantees, private origins and image processing call for services designed for those requirements.

Use casesProductsPricing and termsDocumentationSupport resources

Why we recommend it

  • Covers several common Git platforms and provides npm package file URLs.
  • Explicit versions and file paths offer a straightforward way to organise public assets.
  • Published file-size and anti-abuse limits define the scope of the free service.

Considerations

Stay within public repositories and the 25MB file limit, pin versions and retain copies of essential assets. Migrate away from the disabled /img/ endpoint, and treat sponsorship separately from enterprise service guarantees.