View source is dead. See how the browser renders a page, not just what the server sends.
Total ratings
4.51
(Rating count:
37)
Review summary
Pros
- Useful for comparing rendered and source code
- Great for SEO and QA needs
- Keyboard shortcut functionality is praised
- Good execution of the tool
- Works well for finding issues in development
Cons
- Does not work on many sites recently
- Issues with capturing JavaScript generated HTML
- Keyboard shortcut conflicts with typing Umlauts
- Lacks a dark mode option
- Does not allow for comparing different DOM states easily
Most mentioned
- Has been useful for many occasions
- Suggested feature for dark mode
- Requests for better HTML visualization for Shadow DOM
- Complaints about functionality breaking recently
- Excellent feedback on usability
Upgrade to see all 60 reviews
Recent reviews
Recent rating average:
3.80
All time rating average:
4.51
Upgrade to see all 60 reviews
Rating filters
5 star 4 star
3 star
2 star
1 star
Date | Author | Rating | Lang | Comment |
---|---|---|---|---|
2024-07-24 | Caden Williamson | en | This seems like an amazing tool over "Ctrl + U" Could you add a dark mode option? | |
2024-06-27 | Crystal Carter | en | An essential bit of tech. I've been using it for years. Great stuff! | |
2024-06-19 | Chris Lever | en | @john you already know I love this extension - used it for years now. Suggestion - can you add an additional code highlighter for shadow DOM? I'm really struggling to distinguish shadow DOM vs Rendered using your extension. We're connected on LinkedIn, message me if you need more info. Cheers, Chris | |
2024-04-21 | Gehteuch nichtsan (RFDarter) | en | does simply not work. html code gerateed with js is not shown at all | |
2024-03-16 | Hiba Abdelkarim | |||
2024-02-15 | Kaj Kandler | en | A great idea with good execution. However there is a small detail that makes it unusable for me. It is called up on the keyboard shortcut "Option+U", which is needed to type an Umlaut on an a qwerty keyboard. So I can't type umlaut anymore, because instead it calls up this tool. | |
2023-12-27 | Suzanne Edelman | en | seems cool but it loses the $_POST so it's useless to me. | |
2023-12-20 | Javier Fernández Morell (Javier Morell) | en | Hi, it would be very very useful if there was a checklist of the things I want to compare, so that I don't have to see the whole website code but just the elements I want. For instance, I just want to see differences in <link rel="canonical"> <meta name="robots"> and <title> tag, for the source code and rendered code. If I could see them at a glance, it would make this tool much more useful. Thanks! | |
2023-11-29 | Steve Green | en | It's quite useful, but it doesn't work when I select the site access option "When you click the extension". I get the error message "Error getting rendered source. Return to site and re-launch View Rendered Source again" in the Rendered panel of the results page. I am testing this on our own website www.testpartners.co.uk. I can live with that and just change the setting to allow access to the website I am testing, in which case it works fine. Having used it for a couple of days, it would be much more useful if it could compare two snapshots of the DOM. On some websites almost the entire body changes on page load, so it's virtually impossible to identify any subsequent changes. I would like to be able to put a page into one state, take a snapshot of the DOM, put the page into a different state and view the changes in the DOM. | |
2023-08-05 | Nenad Stojkovic | Amazing extension, keep the outstanding work!! |
Upgrade to see all 60 reviews