Skip to content
Ask Claude about any Chrome extension, answered with Ext Watch data. See how →
Developer Tools extension

View Rendered Source

View source is dead. See how the browser renders a page, not just what the server sends.

by Peg Leg Ltd · 3 listings

Add to RadarChrome Web Store Free plan tracks 1 extension · no card
extwatch.com/extensions/view-rendered-source-ejgngohbdedoabanmclafpkoogegdpob
View Rendered SourcePeg Leg Ltd · Developer ToolsMedium access
Users
30K+
#341 of 31,192 in category
Rating
4.39
41 ratings · median 4.63
Version
5.0.2
713 KiB · Manifest V3
Access
Medium54/100
2 permissions + every website
From the store listing

Screenshots

5 images from the publisher · use the arrows or pick one · swipe or pick one

View Rendered Source screenshot 1View Rendered Source screenshot 2View Rendered Source screenshot 3View Rendered Source screenshot 4View Rendered Source screenshot 5
1 / 5

Description

As written by the publisher on the store

Compare a page's raw HTML with its rendered DOM, and see exactly what JavaScript changed.

Search engines and AI crawlers do not always run JavaScript. View Rendered Source shows you what your server sends, what the browser builds, and the difference between them, line by line.

📰 Featured in Search Engine Land, Ahrefs, Search Engine Journal

━━━━━━━━━━━━━━━━━━━━

🔍 SEE THREE PANELS, SIDE BY SIDE

  • Raw Source: the HTML the server sends, before JavaScript runs. The same as "View Source", auto-formatted for easy reading.
  • Rendered DOM: the page after the browser builds it and JavaScript runs.
  • Difference: every line that JavaScript added, removed or changed, highlighted so you can spot the unexpected.

━━━━━━━━━━━━━━━━━━━━

📈 FOR SEOs

JavaScript can hide, change or break the tags search engines care about. Use the SEO filter in the Difference panel to see only those tags, and exactly how they changed when the browser rendered the page:

  • Titles, meta descriptions and robots tags
  • Canonicals and hreflang
  • Headings and links
  • Structured data (JSON-LD)
  • Find problems such as:
  • A noindex tag that JavaScript adds
  • A canonical that exists only after rendering
  • A tracking pixel that closes the <head> early, so your title and canonical fall into the <body>
  • Schema that appears, or disappears, after rendering
  • Much more

Use Inventory to see key page elements in the raw and rendered versions at a glance.

━━━━━━━━━━━━━━━━━━━━

🤖 AI CRAWLERS SEE ONLY THE RAW SOURCE

🚨 GPTBot, ClaudeBot and PerplexityBot do *NOT* run JavaScript. If your content exists only in the Rendered DOM, ChatGPT, Claude and Perplexity never see it. Check the Raw Source panel to see what they get.

━━━━━━━━━━━━━━━━━━━━

💻 FOR DEVELOPERS

React, Vue, Svelte, Next.js and Nuxt can render different HTML on the server and in the browser. The Difference panel shows that mismatch, line by line.

DevTools shows only the live DOM. It does not show the raw HTML the server sent, and it has no diff.

See what tag managers, chat widgets and A/B tests are doing to your page.

━━━━━━━━━━━━━━━━━━━━

✅ FREE FEATURES

  • Raw Source, Rendered DOM and Difference panels
  • SEO filter for titles, canonicals, headings, hreflang, JSON-LD and more
  • One-click inventory of key page elements
  • Find, filter, copy and download in every panel
  • Auto-formatted source with syntax highlighting
  • Light and dark theme

Free forever. No account needed.

━━━━━━━━━━━━━━━━━━━━

⭐ PRO: SAVE, COMPARE AND SHARE SNAPSHOTS

Migrating, redesigning or shipping to production? Take a Snapshot before, and compare after.

📸 Snapshots: save the raw, rendered and diffed source with a capture date and a private note
📚 Snapshots library: filter by date, title, URL or note, and reopen any Snapshot

⚖️ Compare any two Snapshots: before and after a migration, or staging and production

🔗 Share a public link: anyone can open it, no extension needed

✉️ Email support

Try Pro free for 7 days.

━━━━━━━━━━━━━━━━━━━━

🚀 HOW TO USE

1️⃣ Open any web page.
2️⃣ Click the View Rendered Source icon, right-click the page, or press Alt+U.

3️⃣ Compare the Raw Source, Rendered DOM and Difference panels.

━━━━━━━━━━━━━━━━━━━━

https://viewrenderedsource.com
💬 Problems, questions or suggestions? Email hello@viewrenderedsource.com

Ratings and reviews

Split of the 37 written reviews we hold
Reviews on the store
4.3941 ratings on the store
37 written reviews we hold
5 ★70.3%26
4 ★10.8%4
3 ★8.1%3
2 ★2.7%1
1 ★8.1%3
Jon Schlottig

I haven't put it's through it's paces yes so I may change this rating but it seems to be very useful for working with AI, one of the more valuable extensions i've seen from a an enterprise competitive intelligence and exploitation potential perspective.

J Ender

Appears default website (https://viewrenderedsource.com/) for this app got captured by squatters. Does the extension allow code to be injected from its origin website? [email hidden]

Ejiro Esiri

The tool is useful, but I’ll use it with caution. I mistakenly flagged an issue because I relied on it without verifying. While comparing raw and rendered HTML for our website’s mobile version, I noticed a discrepancy in the image folder paths. The raw HTML displayed the correct mobile version, but the rendered view showed the desktop version instead. It’s a great tool overall, but this issue needs to be addressed.

whatnetworkph

I am not a techy guy, I just heard about it from FB and installed it for SEO purposes. When I click on the extension, there are three different sections, Raw, Rendered and Difference, and in difference section, there is a lot of code in red color, I think it is generated by rank math, should I remove it or not for SEO perposes? My website is https://whatnetwork.ph/

Frank Conijn

Doesn't work at all for me. Installation went fine, but when I right-click on a page and click View Rendered Source, nothing happens. Same thing with clicking the <V> icon. Chrome 148 on Windows 11.

Gehteuch nichtsan (RFDarter)

does simply not work. html code gerateed with js is not shown at all

Radar

Track View Rendered Source on Radar

This page shows the listing as it is today. Add it to Radar and get one email when it changes.

  • Users and rating
  • Store text and screenshots
  • Permissions it asks for
Free plan tracks 1 extension · no card
Ext Watch Radar watchlist cards showing tracked extensions with users, rating, version and latest store change
Guide

View Rendered Source, in plain words

What it is, what to use instead, what it can access and how to fix it.

At a glance

View Rendered Source at a glance

View Rendered Source is a Developer Tools extension by Peg Leg Ltd with 30K users. Chrome Web Store users rate it 4.39 out of 5 from 41 ratings. By users it sits in the top 5% of Developer Tools extensions.

By users
#341of 31,192 in Developer Tools
Rating
4.39category median 4.63
Access
Medium54 of 100

View Rendered Source alternatives

Closest by what they do · users as the store shows them · bars on a log scale
View Rendered Source30K4.39 ★
Chrome extension source viewer100K4.6 ★View Page Source3K4.6 ★Rendering Difference Engine2K5.0 ★view-current-source1K3.1 ★SourceViewer(zvSource)1K4.3 ★
Permissions

Is View Rendered Source safe?

View Rendered Source asks for 2 permissions and access to every website. One of them gives wide access.

Permissions show what it could do, not what it does. See the full permission list.

54/ 100Medium access
View Rendered Source2 permissions · 1 wide
  • <all_urls>Read and change data on every website

Every permission View Rendered Source asks for

2 permissions + every website · 1 sensitive · Medium access overall

Sites

  • Read and change data on every websitehttp://*/*

Browser permissions · 2

  • Add items to the right-click menucontextMenus
  • Save its own settingsstorage

Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.

Troubleshooting

View Rendered Source not working?

What recent reviews say

Store reviews from the last 90 days

No new reviews were posted in the last 90 days, so there are no fresh complaint signals.

Common fixes

Try them in this order
  1. 1Update Chrome and the extension
  2. 2Turn it off and on in chrome://extensions
  3. 3Reload the page
  4. 4Turn other extensions off in case two clash

Still stuck? Contact the maker or try an alternative.

298,549 Chrome extensions in one place

Know when a listing changes

Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.

No credit card neededFree ExplorerAsk Claude about any extension