Turn your browser into a visual content editor

Blip lets you click "Edit" on any webpage, change the text directly on the live page, and save a structured before/after diff. If you connect a repo, Blip saves the change directly. If not, you get a clean diff you can copy and share. It lets you edit text and markdown files in the same ways.

Blip can edit text and capture diffs on any website or web application. GitHub sync works best with flat-file HTML sites, including vanilla HTML, Alpine.js, Astro, and HTMX sites deployed from a GitHub repository.

No account is required to edit pages, save diffs, or export them. You only need a GitHub account if you want to commit edits directly to a repository you can access.

No. Blip uses the browser's built-in designMode to make text editable. It never modifies your actual files unless you explicitly click Save with a repo connected. Every edit is a clean git commit you can revert.

GitHub sync works where content lives in HTML files: vanilla HTML/CSS/JS, Alpine.js, HTMX, Astro, jQuery, and similar sites. React, Next.js, Vue, and Svelte are not supported for source sync when content is generated from component state. Blip can still capture visual diffs on those sites.

Yes. Blip has no paid tier. Its source code is available on GitHub under the GNU General Public License v3.0, so you can inspect, use, modify, and share it under that license's terms.

Yes, that's one of the main use cases. Edit their site in your browser, copy the diff from the sidebar, and paste it into an email or Slack message. They get a clean before/after showing exactly what you changed.

DevTools lets you edit the DOM in some cases, not as comprehensively as Blip. Also, your changes vanish on reload and there's no record of what you changed. Blip captures a structured diff with before/after context, persists edits across pages, and can save directly to your source files via Github.