# GitHub Diff Views Explained: Rendered Prose vs Source Comparison > Master GitHub diff views. Compare rendered prose and source code side-by-side to analyze changes effectively. Understand markup vs HTML for seamless review. - Repository: [Tim Green/github-cheat-sheet](https://github.com/tiimgreen/github-cheat-sheet) - Tags: deep-dive - Published: 2026-03-06 --- **GitHub provides two distinct diff visualization modes—the default source view displaying raw markup with +/- symbols and the rendered prose view showing formatted HTML—enabling developers to toggle between syntax editing and visual review without altering the underlying diff data.** When reviewing documentation changes in pull requests or commits, understanding GitHub's dual visualization modes is essential for efficient collaboration. The **tiimgreen/github-cheat-sheet** repository documents these features extensively in its [`README.md`](https://github.com/tiimgreen/github-cheat-sheet/blob/main/README.md) file, specifically within the "Rendered Prose Diffs" section. This guide examines the technical architecture and practical applications of both source and rendered prose diff views to streamline your documentation review workflow. ## Source View vs Rendered Prose: Key Differences **Source view** is the default visualization mode when opening any commit or pull request on GitHub. It displays the raw markup—such as Markdown, reStructuredText, or AsciiDoc—with standard `+` and `-` diff symbols indicating line additions and deletions. This mode is essential when you need to debug broken syntax, adjust formatting, or compare exact character-level changes. **Rendered prose view** transforms the raw markup into its final HTML representation using GitHub's internal parsing engine. This mode displays exactly how the document will appear to readers, making it invaluable for reviewing heading hierarchy adjustments, table formatting, or list structure changes where visual presentation matters more than underlying syntax. The toggle between these modes occurs entirely client-side in your browser; the underlying diff data and URL remain identical regardless of which visualization you select. ## The Technical Architecture Behind Rendered Diffs According to the source documentation in **tiimgreen/github-cheat-sheet**, GitHub implements rendered prose diffs through a specific processing pipeline: 1. **File Type Detection**: GitHub's **Linguist** library analyzes the changed files to identify supported markup formats. 2. **Markup Parsing**: The raw content passes through the **GitHub-Flavored Markdown** parser (or appropriate renderer for other formats), converting lightweight markup syntax to HTML. 3. **Client-Side Transformation**: The UI renders a **"rendered"** button above diffs containing compatible markup files. Clicking this button triggers a browser-side transformation that displays the parsed HTML while preserving the original `+` and `-` context indicators. Because this is a presentation-layer switch, the rendered prose view does not reload the page or modify the underlying diff data; it merely changes how the changes are displayed in the browser interface. ## When to Use Each GitHub Diff View Use **source view** when performing tasks that require visibility into the underlying markup syntax: - Debugging broken Markdown tables or malformed code fences - Adjusting heading levels by modifying hash symbols (`#`, `##`) - Comparing line-by-line changes where whitespace or punctuation differences matter - Reviewing changes to non-markup files where rendered view is unavailable Use **rendered prose view** when the final visual output is the primary concern: - Verifying that documentation headings render at the correct hierarchy levels - Confirming that tables display properly with aligned columns - Checking that code blocks appear with correct syntax highlighting - Reviewing prose edits where reading flow and formatting are more important than syntax specifics ## Accessing Raw Diffs via URL Parameters While the UI toggle switches between visual presentations, GitHub also provides direct programmatic access to raw diff data through URL modifications. Append `.diff` or `.patch` to any pull request URL to retrieve plaintext source diffs suitable for local analysis or command-line tools: ```bash # Standard PR page showing source view with UI controls https://github.com/tiimgreen/github-cheat-sheet/pull/15 # Raw diff format for local review or archiving https://github.com/tiimgreen/github-cheat-sheet/pull/15.diff # Patch format suitable for git apply commands https://github.com/tiimgreen/github-cheat-sheet/pull/15.patch ``` Adding `?w=1` to a standard commit or PR URL hides whitespace-only changes in the source view, though this parameter does not enable the rendered prose visualization. ## Summary - **Source view** displays raw markup with `+` and `-` symbols and serves as the default visualization for all diffs. - **Rendered prose view** shows formatted HTML output and is toggled via the **"rendered"** button above compatible markup diffs. - The **tiimgreen/github-cheat-sheet** repository documents this feature in [`README.md`](https://github.com/tiimgreen/github-cheat-sheet/blob/main/README.md) under the "Rendered Prose Diffs" section. - GitHub's **Linguist** library and **GitHub-Flavored Markdown** parser handle the client-side transformation from markup to HTML. - Append `.diff` or `.patch` to PR URLs to retrieve raw plaintext diffs for offline analysis or automated processing. ## Frequently Asked Questions ### How do I switch to rendered prose view in GitHub? Look for the **"rendered"** button that appears above the diff when viewing changes to supported markup files like Markdown or AsciiDoc. Clicking this button switches the display from raw markup syntax to formatted HTML without reloading the page or changing the underlying diff data. ### Does rendered prose view change the actual diff content? No, the rendered prose view only affects the presentation layer in your browser. GitHub's diff engine processes the raw source text unchanged; the **Linguist** library and **GitHub-Flavored Markdown** parser transform the display client-side while preserving the original `+` and `-` context indicators around the rendered output. ### Can I share a direct link to the rendered prose view? No, GitHub does not use separate URLs for the two view modes. Both source and rendered views share the same pull request or commit URL, with the toggle controlled by client-side JavaScript. To share a specific view, you must instruct collaborators to click the **"rendered"** button after opening the standard URL. ### What file types support rendered prose diffs? GitHub supports rendered prose diffs for markup languages including Markdown, reStructuredText, and AsciiDoc. The **Linguist** library automatically detects these file types and enables the **"rendered"** toggle when viewing changes to compatible documents in repositories like **tiimgreen/github-cheat-sheet** or any other project using these formats.