Roadmap

What works today, and where this is going

I’m building pdf·markdown in the open, on my own — just me and a keyboard 👨‍💻. So here’s the honest status — what it already does well, what still breaks, and what I’m working on next.

No roadmap theater, no dates I can’t keep. Just where things actually stand, kept current as it changes. If a PDF comes out wrong, that’s not a footnote here — it’s the point of this page. Telling me is the fastest way to get it fixed.

What it does well right now

Where it’s still rough

The honest list of where conversions can break today. If you hit one of these, I’d rather you knew going in.

A few of these run up against what a browser tab can realistically do. I’m still hunting for better in-browser ways to handle them — and some may ultimately depend on the server-side option below.

Hit one of these? Tell me which file broke — that’s what moves it up the list. I never see your file unless you choose to attach it.

What I’m working on next

Roughly ordered, not scheduled. What you tell me reshuffles it.

Now

  • Tightening table fidelity — the single most-reported rough spot.
  • Smoothing the proofread-and-fix pass so corrections are quicker.

Next

  • Better OCR, so scanned PDFs convert more reliably.
  • Better handling of multi-column academic layouts.

Maybe

  • Converting several files in one go.
  • A server-side option for the heavy jobs (more below).

The bigger picture: a server-side option, maybe

Everything a browser can do, I want to do as well as it can be done — and your files will always stay on your machine here. That’s the whole point.

But several of the hard cases above — better OCR, complex tables and formulas, vector-drawn figures, big batches — are genuinely tough inside a browser tab. For those, there may one day be an optional server-side path to pick up where the browser runs out of room.

Two honest caveats: it’s a direction, not a dated promise — and a server path means your file would leave your device, so it’d always be a clearly-marked choice, never the default. The in-browser tool stays the free, private main event regardless. Whether I build the server side at all, and what it should do, depends on what you tell me you actually need.

Recently shipped

This page is only honest if you help keep it that way. If something broke, felt clunky, or you wish it did one more thing — that’s exactly what I want to hear.