TransformPipe

TransformPipe

Turn a Word file, a web page or a whole Notion export into a clean document, keep it, and send it as a page with one link.

Open it · Documentation · Browser extension · What has shipped · Support

Documents arrive in the wrong shape. A Word file you need as Markdown. A Notion export that is forty pages in a zip. A spec your assistant wrote, gone once the chat scrolls away. Markdown pasted into an email, landing as a wall of asterisks.

TransformPipe turns all of them into one thing: a clean Markdown document. See it as a finished page, take it away as Markdown, HTML, Word, PDF, Confluence, Jira, Slack or EPUB, or keep it and send a link instead of an attachment. Open transformpipe.com and drop a file. No account is needed to convert.

Twenty conversions, in your browser

Word, PowerPoint, Excel, EPUB, OpenDocument, rich text, HTML, CSV, JSON, plain text, Evernote, or a whole Notion, Confluence or Obsidian export. Each comes back as Markdown with its headings, lists, links and tables intact, and Markdown goes the other way: into a finished page, a Word document, a Confluence page, a Jira ticket, a Slack message or an EPUB book.

The conversion runs on your machine. Signed out, nothing is uploaded and nothing needs a network. Drop several files and they become one document, in the order you picked them.

Markdown in, a finished page out

Tables, code, task lists, maths and Mermaid diagrams come out the way they were meant to look. The download is one self-contained .html file that fetches nothing when it opens: no scripts and no webfonts. A saved document also downloads as Word, and any document prints to PDF.

Send a link, not an attachment

Share a saved document with anyone who has the link, or only with the addresses you name. Give the link a password or an end date if it needs one, and see how often it was opened. Make private stops it in one step, and the old link stops working for good.

Publish new text from the API, the command line, an assistant or Obsidian, and the link people already have shows it. The text it replaced is kept as a revision.

What your assistant writes, kept

TransformPipe is in Claude's connector directory: press Connect, sign in, and ask in plain words. "Save this as the Q3 plan." "Publish it and give me the link." "Find the migration spec from last week." The document goes into your account, with a title you can search for, long after the chat has scrolled away.

ChatGPT connects too, by address, as an MCP app, and Obsidian has a community plugin. All three see the same documents.

One library, not forty chats

Everything you convert, save or have an assistant save lands in one list: searchable, filtered by format, with versions side by side and a line-level diff between them. Signed in, it is the same list on every device.

Any web page, as Markdown

The browser extension, for Chrome and Firefox, takes the page you are on and hands back the article without the navigation or the cookie notice. Copy it, download it, or save the page as a self-contained .html file. Signed out, it never talks to us.

Your documents, your account

An assistant acts as you, on your documents only. It cannot change the account, see your password or create API keys, and it deletes nothing without an explicit confirmation. A grant can be read-only. The service is free, and the limits are written down: 5,000 documents and 250 MB an account, 4 MB a document. Reaching one refuses the save; nothing is deleted to make room.

Every way in

• The web app at transformpipe.com: convert, preview, keep and share.
• Claude, from the connector directory on claude.ai and in Claude Desktop, or by address in Claude Code.
• ChatGPT, as an MCP app: the three steps.
• The [browser extension](https://transformpipe.com/extension), for Chrome and the browsers built on Chromium, and for Firefox on the desktop and on Android.
• [TransformPipe for Obsidian](https://community.obsidian.md/plugins/transformpipe): publish a note as a page, and keep the same link after every edit.
• A script: the API, the command line and a GitHub Action.

---

Conversions

Live at [transformpipe.com](https://transformpipe.com). The old md-2-html.vercel.app still answers, so links already shared keep working; the canonical URLs, the sitemap and every default in the CLI and the Action name the new domain. Nothing in server/ carries a domain at all — origins come from the request through selfOrigin, which is what made the move a matter of one trusted origin and a rebuild.

Upload a file, see exactly what it became, and download it. Twenty conversions, each with its own page and address:

They all normalise to Markdown, which is what a document is stored, previewed, shared and reached by a script as — one shape rather than fourteen. Any document can then be handed over as Markdown, HTML, plain text, Word, Confluence, Jira, Slack, EPUB, or printed to PDF. shared/conversions.ts is the single list; the header menu, the screens, the history chips, the badges and the prerendered pages all read it, so a new conversion is an entry there plus a converter.

.txt used to be accepted on the Markdown → HTML page as if it already were Markdown; it has its own conversion now instead, because a plain-text file is not Markdown even when it looks like it — an asterisk typed as a literal asterisk and one meant as emphasis are the same character, and only one of the two conversions is supposed to treat them alike.

Notion, Confluence and Obsidian are the three that do not produce one document from one file: each export is several pages (or notes) in a .zip, and each comes back as a single Markdown document — a table of contents, then every page in order, each a heading of its own (shared/from-notion.ts, shared/from-confluence.ts, shared/from-obsidian.ts, sharing the zip-reading and merge convention in shared/zip-import.ts). A link from one page to another inside the export keeps its words and drops its address — Obsidian's own [[wikilinks]] included: once every page is a section of one document, there is nowhere left for it to point.

Conversion happens in the browser — the .docx reader and the HTML parser load only when their page is used, so the front page's bundle does not carry them. Sign in — with Google, or an email and a password — to keep your documents in the account and reach them from any device.

Run locally

npm install

cp .env.example .env.local # then fill in the values (see Configuration) npm run db:init # creates the table in Neon npm run dev

The app starts on http://127.0.0.1:5180 — /api/* is served by the same Hono app that runs as a Vercel function in production, so no extra process is needed.

Other scripts: npm run build, npm run preview, npm run check-types, npm run db:init.

Without NEON_AUTH_BASE_URL the app still converts files: sign-in answers 503 and the history falls back to this browser's localStorage.

Configuration

Both are server-side only; the browser talks to /api/* and never to Neon directly.

Sign-in is Neon Auth (Better Auth behind a Neon endpoint), which already carries Google — no separate Google OAuth client and no client secret here. /api/auth/* forwards to the auth service and rewrites Set-Cookie so the session cookie is first-party for this site; /api/auth/finish exchanges the one-time verifier for that cookie. See server/auth.ts.

Neon Auth only starts a sign-in for an origin it trusts, so each origin has to be added once — and this is the whole of what breaks when the site moves to a new domain: everything else derives its URLs from the request, and sign-in is the one thing that has to be told:

npm run auth:orig