AI Markdown

How to Open a ChatGPT Deep Research Report (.md)
with tables and footnotes intact

A ChatGPT Deep Research report is long, and it usually comes with tables, numbered citations, and sometimes math. When you save or copy it into a .md file and open that in a plain text editor, the tables collapse into rows of pipes, the citations become [^1] text, and the whole thing reads like markup.

The file is fine. It just is not being rendered. Here is how to open that .md and read the report the way it was meant to look, locally, without uploading the file.

Open your deep research .md and read it rendered, right in the browser →

Why the report looks broken in a plain editor

A Deep Research report saved as Markdown leans on a few things that a plain editor does not render:

  • Tables are written in GFM pipe syntax, so you see | ... | ... | rows instead of a table.
  • Citations are often Markdown footnotes, so a source shows as [^1] instead of a linked reference.
  • Math, if the report has any, shows as raw LaTeX between dollar signs.

None of that is corruption. It is ordinary Markdown that needs a reader which renders GFM tables and footnotes. This is the same underlying issue as Markdown not rendering in general.

Open it rendered, in the browser

NoteLoom opens a local folder right in the browser and renders the .md files in it, which is exactly what a long report needs.

  1. Save or copy the Deep Research report into a .md file (for example in your Downloads folder).
  2. Open app.noteloom.cc in Chrome / Edge / Arc and mount that folder. Nothing to install.
  3. Open the report in Reading view. The tables, footnote citations, headings, and any math render, so you can read the whole thing section by section.
In the report In NoteLoom’s Reading view
GFM tables A real table instead of rows of pipes and dashes
Footnote citations [^1] Numbered, linked references you can jump to
Math ($ ... $) Rendered with KaTeX instead of raw LaTeX
Headings and sections A long report you can scan and read section by section

The honest limits

To be clear about what this does and does not do:

  • It renders, it does not export or convert. You bring the report as a .md file; NoteLoom opens and displays it. It cannot repair markup that the export itself mangled.
  • Opening the report does not touch its wording. Rendering shows the file you already have, word for word. Nothing is summarized, re-run, or rewritten on the way in.
  • The file never leaves your machine. It is read locally in the browser, not uploaded, and reading works offline.
  • The AI chat panel does send data out. If you open it and send a message, that message goes to the model, along with any note text the model pulls in through a tool call. You have to open the panel and ask. Reading a report does not.

If you are also wrangling shorter answers, see opening the Markdown ChatGPT gives you and reading long AI plans and reports.

Related reading

How to open the Markdown ChatGPT gives you The general version, for any answer, not just a long research report.
How to read long AI plans and reports Making a wall of AI-generated Markdown actually readable.
How to make a table in Markdown Why the report’s tables show as pipes, and what renders them.
How to add footnotes in Markdown The [^1] citations in the report, and how they link.

FAQ

How do I open a ChatGPT Deep Research report as Markdown?
Save or copy the report into a .md file, then open that file in a Markdown reader. In NoteLoom you open your browser, mount the folder where it is saved (like Downloads), and open the .md; Reading view renders the tables, footnote citations, and math instead of showing raw text.
Why do the tables and citations look broken in the file?
In a plain text editor, GFM tables show as rows of pipes and dashes and footnote citations show as [^1], because nothing is rendering the Markdown. It is not corrupted. Open it in a tool that renders GFM tables and footnotes and they turn back into a real table and linked references.
Does NoteLoom fix a broken Deep Research export?
It renders a well-formed .md. If the report is saved as valid Markdown, NoteLoom shows the tables, footnotes, and math properly. It cannot repair markup that the export itself mangled, because that is on the tool that produced the file. Opening a file renders it in place; the render does not convert the file or rewrite what is on disk.
Is my research report uploaded anywhere?
Opening it does not upload anything. NoteLoom reads the local file in your browser through the File System Access API, and reading works offline as a progressive web app, so the report stays on your own machine. The AI chat panel is different: if you open it and send a message, that message goes to the model, along with any note text the model pulls in through a tool call. Reading a report never does that on its own.
Will opening the report change it?
It opens and renders the .md file exactly as you saved it, so the citations, headings, and tables stay as they are. Opening a report does not re-run it or rewrite its wording. Reading never writes to the file.
Which browser do I need?
A Chromium-based desktop browser: Chrome, Edge, or Arc. It uses the browser’s File System Access API.

Read Deep Research Reports Formatted and Offline

Save your comprehensive Deep Research report as a .md file, open NoteLoom in Chrome or Edge, and read it with pristine tables, citations, and headings. Your confidential research stays on your disk.

Open Local Report in Browser →

Published · Updated