The last Markdown editor you'll ever need.

A modern, cloud-native Markdown editor built on Next.js — designed for speed, focus, and seamless sync.

Get Started · Features · Integrations · Deploy

Most markdown editors are either:

• bloated
• offline-only
• or lack serious developer ergonomics

Dillinger fixes that.

It combines:

• ⚡ VS Code-grade editing
• ☁️ Native cloud storage
• 🧘 Distraction-free UX
• 🔄 Real-time rendering

npm install
npm run dev

Open → http://localhost:3000

• Node.js 18+
• npm / yarn / pnpm / bun

• Monaco Editor (VS Code core)
• Syntax highlighting for Markdown
• Image paste support

• Real-time preview
• Scroll sync
• Instant feedback loop

• Zen Mode (Cmd/Ctrl + Shift + Z)
• Fullscreen, distraction-free writing

• Drag & drop .md, .txt, .markdown
• Auto-save (local persistence)

• Markdown
• HTML
• PDF

• GitHub
• Google Drive
• Dropbox
• OneDrive
• Bitbucket

Create:

.env.local

# Google Drive
GOOGLE_CLIENT_ID=
GOOGLE_CLIENT_SECRET=
GOOGLE_REDIRECT_URI=http://localhost:3000/api/google-drive/callback

# OneDrive
ONEDRIVE_CLIENT_ID=
ONEDRIVE_CLIENT_SECRET=
ONEDRIVE_REDIRECT_URI=http://localhost:3000/api/onedrive/callback

# Bitbucket
BITBUCKET_CLIENT_ID=
BITBUCKET_CLIENT_SECRET=
BITBUCKET_REDIRECT_URI=http://localhost:3000/api/bitbucket/callback

# GitHub
GITHUB_CLIENT_ID=
GITHUB_CLIENT_SECRET=
GITHUB_REDIRECT_URI=http://localhost:3000/api/github/callback

# Dropbox
DROPBOX_CLIENT_ID=
DROPBOX_CLIENT_SECRET=
DROPBOX_REDIRECT_URI=http://localhost:3000/api/dropbox/callback

Each provider requires OAuth configuration.

• Enable Drive API
• Create OAuth credentials
• Redirect:

/api/google-drive/callback

• Azure App Registration

• Permissions:

  • Files.ReadWrite
  • User.Read

• OAuth consumer
• Repo read/write access

• OAuth App
• Callback:

/api/github/callback

• Scoped app

• Enable:

  • files.metadata.read
  • files.content.write

Update all OAuth callbacks:

https://yourdomain.com/api/{provider}/callback

Then:

npm run build
npm start

npm run dev              # Start dev server
npm run build            # Production build
npm start                # Start production server
npm run lint             # ESLint
npm run test             # Unit + E2E tests
npm run test:unit        # Vitest unit/integration tests
npm run test:watch       # Vitest watch mode
npm run test:e2e         # Playwright E2E tests
npm run test:e2e:headed  # E2E in visible browser
npm run verify           # Lint + typecheck + all tests

294 unit/integration tests (Vitest) + 39 E2E tests (Playwright) with 98% code coverage.

npm run test:unit                # Run all unit tests
npx vitest run --coverage        # With coverage report
npm run test:e2e:headed          # E2E in visible browser

Tests live in tests/ organized by type: lib/, store/, hooks/, components/, routes/, and e2e/.

Dillinger is built around a simple idea:

Writing tools should disappear.

No friction. No clutter. Just flow.

PRs welcome. Open an issue first for major changes.

MIT