Reading AI documents when you think in pictures

Why does a .md file from Claude look like a wall of symbols?

A .md file from Claude or ChatGPT looks like a wall of symbols because it arrives as raw Markdown, written for software to format. AI has made writing fast. You can get a project plan, a research summary or a spec in a couple of minutes. Then it arrives as a .md file, and when you open it you see this:

## Q4 priorities
**Owner:** Maya | **Status:** draft
- Ship **path-paste** first
  - then folder tabs
| item | due |
|---|---|
| beta | Oct 1 |

Some people read that easily. Many don't. If you're someone who understands by seeing the shape of things, where the headings are, what's grouped with what, how big each section is, raw Markdown hides exactly the information you rely on.

It's easy to assume the problem is you. It usually isn't. The file was written for software to format. You're being asked to do the formatting in your head.

you're not bad at reading. you're doing the app's job.

Why is raw Markdown tiring for visual thinkers?

Raw Markdown is tiring for visual thinkers because it hides the shape of a document: headings, groups, tables and processes all become lines of symbols. People read in different ways, and there's no single "visual learner" type that fits everyone. But many people report the same experience with raw Markdown, and the reasons are easy to see.

The structure is written, not shown

In a formatted page, a heading is large and has space around it. You see the outline before you read a word. In raw Markdown, a heading is a line that starts with ##. It's the same size as everything else. To find the structure, you have to read for it.

Symbols compete with words

Every **, backtick and bracket is a small interruption. Each one is easy to decode on its own. Across a long document, they add up. Your attention goes to the symbols instead of the meaning.

Tables and processes lose their shape

A table is a grid. A process is a sequence with branches. Both are shapes. Raw Markdown flattens them into lines of pipes and arrows made of dashes, so you have to rebuild the shape mentally before you can understand it. That's the moment many people give up and copy the text into something else.

Long, even walls of text

AI output tends to be long and evenly paced. Without visual variation, bold terms, spacing and sizes, there's nothing to anchor your eye. It's easy to lose your place, and hard to find it again.

What helps visual thinkers read AI documents?

Visual thinkers read AI documents more easily by changing what they look at. You don't have to read harder.

1. Look at the formatted page, not the file

Looking at the formatted page is the biggest single change. When the same document is formatted, headings have size, tables are grids, lists have clear levels and code sits in its own box. The information is identical. The effort isn't.

Set a Markdown reader as the default app for .md files on your Mac, so double-clicking opens the formatted page. Our guide to opening a .md file on a Mac shows how.

2. Read the outline first

Before reading any paragraph, look at the headings. In a reader with a headings sidebar, that's one glance. You learn how long the document is, what it covers and where the part you need lives. Then jump straight there.

If you only have raw text, scroll through and look only at lines that start with #.

3. Turn structure into pictures

Ask for, or look for, visual forms of the information:

• Processes as flowcharts. A Mermaid flowchart, drawn by your reader, shows branches and loops at a glance. See how to read Mermaid diagrams.
• Comparisons as tables. Rendered properly, a table lets you compare down a column without counting. See Markdown tables that are actually readable.
• Plans as timelines. A Gantt chart shows overlap and order that a list of dates hides.
• Progress as checklists. Ticked boxes show what's left far faster than a list of brackets.

4. Make the page fit your eyes

Everyone's comfortable reading setup is different. Some people read best with a large serif font and generous line spacing. Others prefer a clean sans serif, a narrower column and a warm background. Some find dark mode easier, others find it harder.

Try changing one thing at a time: font size, line spacing, column width, background. Notice which change makes the page feel calmer.

In One Clear Reader, the Aa button holds ready-made reading profiles. This table shows three of the free ones and when to try each.

Atkinson Hyperlegible was designed by the Braille Institute to be easier to read for people with low vision (Braille Institute).

In One Clear Reader you can also change text size and page width, and pick a page color. Paper, Night and Mist are free, and Pro adds the rest of the 22 themes (some are light and dark versions of the same design). Full View fills the screen with the page, so wide tables and diagrams have room to spread out. With Pro, a Custom profile lets you set every font and spacing yourself and save your own named profiles to switch between.

For fonts and settings aimed at dyslexia and ADHD, see reading on a Mac with dyslexia or ADHD.

5. Give yourself anchors

Bold key terms, summaries at the top of sections and clear dividers all give your eye somewhere to land. If the AI didn't include them, ask it to.

How do I ask Claude or ChatGPT for documents that read better?

You can ask Claude, ChatGPT or Cursor for documents that read better by adding a few lines to your requests, or to your standing instructions:

• Start with a three-sentence summary.
• Use short sections with clear headings.
• Keep paragraphs to three sentences or fewer.
• Bold the key term in each section.
• Use a table for any comparison, and add one sentence saying what it shows.
• Show any process as a Mermaid flowchart, top to bottom, with short labels.
• End with a checklist of next steps.

These don't only help you. They make documents easier for everyone to skim, including the colleague you forward it to.

How do I set up my Mac so AI documents arrive readable?

Five steps set up a Mac so AI documents arrive readable.

1. Give AI files one home. Make a folder such as ~/Documents/AI and point your tools at it. The guide to where AI saves files explains how for each tool.
2. Set a reader as the default for .md. In Finder, select a .md file, press ⌘I, choose your reader under Open with, and click Change All.
3. Open by name, not by folder. In One Clear Reader, type part of a file name, like plan, and pick it from the matches. Or paste the path your AI gave you, or pick the file from Latest from your AI on the welcome screen, which lists what changed in the last 24 hours.
4. Pick a reading profile. Start with Neuro-friendly or Large Print, then adjust text size and page width until the page feels calm.
5. Edit without leaving. When you need to change one line, edit it in the same app (One Clear Reader's Markdown source editor is free). The file stays a clean .md, so your AI can keep working with it.

Is it reasonable to want AI documents to be easier to read?

Yes, wanting AI documents to look like documents is completely reasonable, because formatting exists to make structure easier to see than to decode. And it's a small setup change away.

Many people who work fast with AI quietly struggle with the output. They skim, they copy things into other apps to make them readable, or they just trust the summary at the top and hope. It rarely comes up, because it can feel like admitting you can't keep up.

documents are supposed to look like documents. that's allowed.

Questions people ask