FoldRender / Guides / Make long documents comfortable on a Fold
FoldRender guide

Make long documents comfortable on a Fold

A big unfolded screen makes reading possible; a few settings make it comfortable. This page is the short tour of every reading-comfort control in FoldRender — the Reading sheet, the code wrap toggle, outline navigation, the find bar and per-document scroll position — what each one does, and which to change once and never think about again.

Get it on Google Playfree See what FoldRender does

Step by step

  1. Install from Google Play

    FoldRender is on the Play Store as FoldRender: Repo Reader, package id dev.foldrender.app, free and distributed worldwide. Install it the ordinary way — no allow installs from this source prompt to approve, and updates arrive on their own. The app declares minSdk 30, so it needs Android 11 or newer; Play will tell you if a device is below that rather than letting you install a build that cannot run.

  2. Open the Reading sheet once, set it and forget it

    The text-size icon opens the Reading sheet, which has four controls: a Theme segmented control (System / Light / Dark), a Text size slider from 80% to 160%, a Line width slider from 480 dp to 1200 dp, and a Serif body text switch. The settings persist across documents and sessions, and changing the theme re-renders without re-parsing the document — so toggling dark mode mid-read is instant.

  3. Narrow the line before anything else

    Line width is the setting that matters most on an unfolded Fold. Without it, paragraphs run the entire width of the inner screen and your eyes lose the line on every return sweep. Cap the measure somewhere short of full width — a comfortable column rather than a banner — and long Markdown pages suddenly read like pages. This is the one control most reading apps omit and the one that pays off immediately.

  4. Wrap the code, or don't

    Source files have their own control: a Wrap chip next to the file header. Off, long lines scroll horizontally with the line numbers staying aligned; on, they wrap into the reading column. Folded, wrapping is usually what you want — horizontal scroll on a narrow screen fights the reader. Unfolded with a two-pane layout, horizontal scroll often reads better because the code pane is already the width you chose.

  5. Navigate by outline, not by scrolling

    In a rendered Markdown document, a small floating button in the bottom-right corner opens an outline sheet listing the document's top-level headings, with the one you are inside emphasised; tap a heading to scroll there. Long documents stop being scroll-bar problems. A document with no headings gets “No headings in this document.”

  6. Find inside the document when you're hunting

    The magnifier in the top bar opens the find bar — placeholder Find in document…, a live current/total match counter, and up/down chevrons to step through hits. It appears for text-shaped formats: Markdown, notebooks, JSON/YAML/TOML, CSV, source, logs and plain text. PDFs, images and HTML have no find bar — in a PDF your navigation is the page counter and the tap-to-jump thumbnail strip.

  7. Trust your place to survive

    Scroll position is stored per document and restored when you reopen it, so moving between three files and back does not lose your place in any of them. Combined with the Recent tab and long-press favourites in the tree, a multi-document reading session survives interruptions without any bookmarking ceremony.

How FoldRender handles it

Theme changes are cheap by construction

The Markdown parsers emit no colours and no Compose types — that is why switching theme re-renders without re-parsing. Dark mode mid-chapter costs a relayout, not a re-walk of the document.

The settings apply around the document too

In a PDF, the Reading sheet's theme applies to the app shell around the document, and page bitmaps are cached per page and per width — so rotating or refolding re-renders pages at the new width instead of upscaling a stale bitmap.

Comfort is layout, not just size

Text size is the obvious knob; line width, wrapping and outline navigation are the three that actually decide whether a two-hour read on a folded-out phone feels like reading or like scanning.

Where it stops

The honest list — shipped-but-unverified behaviour included, so you can tell before installing whether this build does the thing you came for.

FAQ

How do I make text comfortable to read on a Galaxy Z Fold 7?
Open the Reading sheet from the text-size icon and set two things: Line width — narrow it well short of the full unfolded width so your eyes don't lose the line — and Text size, 80% to 160%. Theme (System/Light/Dark) and a serif body-text switch round it out. The settings persist.
What does line width actually change?
The maximum width of the reading column. On an unfolded Fold the inner screen is wide enough that full-width prose becomes hard to track; capping the measure turns it back into a readable page. It is the single highest-value reading setting on a foldable.
How do I stop code lines running off the screen?
Use the Wrap chip next to a source file's header. Wrapped, long lines flow into the reading column; unwrapped, they scroll horizontally with line numbers staying aligned. Folded, wrap is usually the better default.
Will dark mode re-parse my document?
No. Switching theme re-renders without re-parsing — the parsers emit no colours and no theme-coupled types, so a theme change is a cheap relayout even in a large document.
Does the app remember where I was in each file?
Yes — scroll position is stored per document and restored on reopen, so a multi-file reading session survives app restarts and device refolds without bookmarks.

More FoldRender guides