HTML to SVG Converter

Wrap an HTML file into a self-loading SVG so it can be served through GitHub-backed CDNs. Already have an .svg? Switch modes in step 2 to skip the conversion and just get your CDN links. Follow the numbered steps below in order, including creating the repo if you don't already have one.
1
Do you already have a GitHub repository?
This is a folder on GitHub.com that will hold the generated file. If you already have one you want to use, skip to step 2. Otherwise, create one now:
Open github.com/new to create a repository ↗
  1. Type any Repository name, e.g. my-svgs
  2. Set visibility to Public. The CDN links in step 6 will not work on a Private repo
  3. Leave everything else as default and click Create repository
  4. You'll land on the empty repo page. Keep that tab open, you'll upload to it in step 6
2
Select your file
This is the source file on your computer. It stays local, nothing is uploaded anywhere by this page.
Drop an .html file here or click to browse
3
Tell it which repo you'll use
Open the repo from step 1 in GitHub and copy its URL from your browser's address bar into the box below. The fields underneath will fill themselves in.
or fill in manually
4
Name the output file
This is the exact filename you'll use when uploading in step 6. You can leave it as "index" if you're not sure. In .svg mode it fills in from your file's name.
5
Generate and download
Check off step 1 and select a file in step 2 to enable this.
Quick recap
  1. Create a public GitHub repo, or use one you already have (step 1)
  2. Pick your .html file, or switch to .svg mode and pick your .svg (step 2)
  3. Paste that repo's URL (step 3)
  4. Name the output file (step 4)
  5. Generate, then download the .svg (step 5)
  6. Upload that .svg to the repo through GitHub's website, then use a link above (step 6)
Limits & troubleshooting jsDelivr's GitHub cap is around 20 MB per file. Base64 adds roughly 33% overhead, so keep source HTML under ~15 MB. A repo must be Public for the CDN links to work. If a link 404s, wait a minute and retry, and double-check the file was actually committed to the branch and path you entered in step 3.