Connect your repo

Beta

PhantomEdit edits Markdown and MDX files directly. Pick where your content lives — your local Astro project, a sandbox that lives only in this browser, or (soon) a GitHub repo. Switching between them is a single click; nothing here is locked in.

Local folder

Unavailable

Point PhantomEdit at your Astro or Next.js project. Files live on disk; saves are real saves; git is your git.

Your content stays in your repo
Works offline
Real .git history

This browser doesn't support the File System Access API. Try Chrome, Edge, Brave, or Arc — or use the Sandbox below.

Sandbox

Try it now

A scratch repo that lives in this browser only. Perfect for kicking the tires before pointing at a real project.

No permission prompts
Survives reloads on this device
Export to a real folder anytime

Your browser doesn't support OPFS. Update to a recent version.

GitHub repo

Coming soon

Connect to a remote repo with a fine-grained PAT. Reads and writes hit the GitHub API; commits are real commits.

Works on Firefox / Safari
Useful for cloud-only editors
Same UI, no backend needed

Phase 2. Want it sooner? Open an issue.

Your content stays yours

PhantomEdit never copies your files anywhere. Local folders are read directly via the browser's File System Access API. The sandbox is encrypted browser storage. There's nothing to log into and no PhantomEdit backend.

Expected layout

PhantomEdit looks for these directories at the root of the connected folder:

astro-content/ — your post-type collections
data/ — settings, post types, taxonomies, fields
public/uploads/ — media library

Don't have them yet? Pick the folder anyway — PhantomEdit will create them as you go.

See how to consume the content from Astro, Next.js, or the REST API →