SOURCE FILES, SERVED PROPERLY

Your repository,
ready for the web.

Turn a public file link into a browser-ready URL. The right headers for your HTML, CSS and JavaScript. No file uploads. No build step.

How it works

Start with a source file

Supported platforms

Use a file link, not a repository homepage.

Try an example:

Your file stays in its repository. This tool creates a link to it.

Pick the link for the job

Put it in your projectEmbed code & integrity

Subresource integrity Optional

For a fixed-version script or stylesheet, add a SHA-384 integrity check.

LESS FRICTION. FEWER SURPRISES.

A link, with the
right instructions.

Read the guide

Serve it as code, not plain text.

Content-Type headers tell browsers how to handle your files. rawgit.net supplies the appropriate type for supported extensions.

A commit makes a better release.

Use a full commit for long-lived production caching. Branches and tags can move, so they keep a short cache.

Your source remains the source.

Files are fetched from their public host. This is a caching proxy, not a permanent archive or a private-file service.

Works with public files on

GitHubGistGitLabBitbucketGiteaCodeberg