PDF to Markdown for VS Code: Edit Documents in Your Editor
You already live in VS Code for code. Converting PDFs to Markdown lets you live there for documents too: split-pane preview, find-in-files, Git-diff for revisions, AI assistance via Copilot or Cursor, all the muscle memory you already have.
The extensions that make this work
The default Markdown experience in VS Code is fine but minimal. Three extensions turn it into a serious document workspace: Markdown All in One (TOC generation, list continuation, table formatting), markdownlint (style enforcement, catches inconsistencies), Markdown Preview Enhanced (math, mermaid diagrams, exporting to HTML/PDF). Together they cover read, edit, lint, and export workflows for converted PDF content.
Why this matters for AI-assisted work
If you use Copilot, Cursor, or a similar AI assistant inside VS Code, those tools read open files and the current workspace. Markdown documents in the workspace become first-class context the AI can reason over, the same way it reasons over your code. PDF attachments don't get this treatment.
Frequently asked questions
What VS Code extensions help with converted Markdown?
Markdown All in One (TOC, formatting, list continuation), markdownlint (style enforcement), Markdown Preview Enhanced (math, mermaid, export to HTML/PDF), and Paste Image (drop screenshots straight into the document). Together they make VS Code a serious Markdown editor.
How do I preview converted Markdown side-by-side with the source?
VS Code has built-in Markdown preview: open the .md file, press Ctrl+K then V (or Cmd+K then V on macOS) for a side-by-side preview that updates live as you edit. Markdown Preview Enhanced adds math, diagrams, and richer styling.
Can I use Copilot or Cursor on converted Markdown?
Yes: both treat open Markdown files as workspace context. Copilot will use the doc when answering questions about it; Cursor's agent will autonomously consult workspace .md files when generating code that depends on documented APIs.
Best way to lint and format converted Markdown?
Use markdownlint with the default config to catch style issues, and Markdown All in One's "Format" command (Shift+Alt+F) to align tables and normalise list markers. Add a .markdownlint.json to your repo if you want team-wide consistency.
Can I version-control converted PDFs as Markdown in Git?
That's the whole point. Markdown diffs cleanly in Git: you can review changes line-by-line, blame edits to specific commits, and revert revisions. PDFs do none of this; their binary format makes Git essentially useless for them.