Render Markdown and ODS files in Bitbucket Cloud pull-request diffs as readable, formatted views with diff highlights.
Users
37
−4 in 30 days
Rating
5.0 / 5
unchanged in 30 days
Ratings
1
0 in 30 days
Store rank
#121K
#101K among extensions
Version
0.4.2
updated 20 Jun 2026
Users
monthly, 5 months
Latest, 16 Oct 2026:37 usersMove the mouse over the chart for any month
Ratings count
monthly, 5 months
Latest, 16 Oct 2026:1 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Bitbucket Rich Diffs
Reviewing a documentation PR on Bitbucket Cloud is the same experience as reviewing code: a wall of plus and minus signs, line numbers, and raw Markdown syntax. Headings look
like "## What it does." Tables look like "| col | col |". Bold text shows as **double-asterisks**. Reading prose this way is slow and easy to skim past.
Bitbucket Rich Diffs adds a small per-file toolbar above every Markdown file in your pull request diffs. One click toggles between three views, and you can mix and match per
file:
ORIGINAL DIFF — Bitbucket's default plus / minus view, untouched.
RENDERED (UNIFIED) — the file rendered as Markdown, in document order, with added blocks tinted green and removed blocks tinted red and struck through. Skim the change like
you'd skim the published doc.
RENDERED (SIDE-BY-SIDE) — two columns: Before on the left, After on the right, both fully rendered. Best for visualizing structural changes like added sections or restructured
tables.
WHY YOU MIGHT WANT IT
Reviewing READMEs, RFCs, design docs, ADRs, runbooks, or any prose under version control. Anyone whose Bitbucket PRs include a Markdown file regularly will save time.
HOW IT WORKS
The extension uses the Bitbucket session you're already signed in with — no separate authentication, no app password, no tokens. Before/after file content is fetched the same
way Bitbucket's own UI fetches source files, and rendered locally in your browser using the marked library. Output is sanitized with DOMPurify before display, so a malicious
Markdown file in a PR can't run script in the page.
PRIVACY
Your data does not leave your browser except for the file-content fetches, which go directly to bitbucket.org over the same connection your normal Bitbucket browsing already
uses. The extension makes no analytics or telemetry calls. There is no account, no settings sync, no third-party service.
OPEN SOURCE
Source code, releases, and issue tracking on GitHub:
https://github.com/thelinuxer/bitbucket-rich-diffs
Released under the MIT license.
WHAT'S COMING
Markdown is the first file format. CSV, JSON, and ODS are on the wishlist.
And for the Summary field above it (max 132 chars):
Render Markdown files in Bitbucket Cloud pull-request diffs as proper formatted documents — unified or side-by-side.