JekyllPad is a small browser tool for people who publish static sites from GitHub. You sign in with GitHub, pick a repository, and write in a visual editor that can flip to raw Markdown. Saving commits the change to the repo. It is built by one independent developer and is not affiliated with Jekyll or GitHub.
Despite the name, it is not limited to Jekyll. The site says it also handles Hugo, Astro, Eleventy and Gatsby repositories. It sits at the lightweight end of the Git-based CMS landscape.
What is its status in October 2026?
The product is live and the site shows a 2023 to 2026 copyright, so it is being kept going. It is a commercial, closed product with a free tier described as free for basic use, with 5 free posts per month. We found no changelog, no public roadmap and no source repository, and the visitor counters on the home page are placeholders. Judge it as a small indie service.
Who does it suit?
A blogger or a founder with a Jekyll or Hugo site on GitHub Pages who does not want to touch Git or YAML. It also works for a one-person documentation site. The browser-only design means there is no server for you to run.
Where are the limits?
- Roles: No role or permission system is described. Access follows who can write to the GitHub repository.
- Branches: Branch support is listed as a future feature, so there is no editorial review through pull requests.
- Media: Image upload is basic, and the site does not state storage limits.
- Schema: It handles frontmatter, but we saw no field validation for structured content.
- Continuity: One maintainer and no published source mean you depend on that person’s plans.
Content stays as plain files in your repo, so the exit cost is low. You lose the editor, not the posts.
When would we use something else?
For a team that needs review before publishing, we would pick Decap or Sveltia CMS, which can run an editorial workflow with pull requests. For the quickest hosted editor with a schema, Pages CMS is a stronger choice, and it is open source. If editors must not need GitHub accounts, look at CloudCannon or Tina. Content that other apps consume, or that many people edit daily, belongs in a full headless CMS.
What can we do for a team on JekyllPad?
- Check that your repository layout and frontmatter are clean enough for any editor, JekyllPad included.
- Add CI checks so a bad edit fails the build instead of reaching production.
- Migrate to a Git-based CMS with schemas and review flow when the blog grows into a business site.
- Rebuild or speed up the site on Jekyll or Hugo.