Reviews (1-10 of 10)
August 30, 2019
- Inspect front-end code.
- Find and debug issues.
- Apply changes in the browser for testing.
- Test responsive designs at various device resolutions.
- Test page speed and performance.
- Test various network situations (e.g. low/no internet connection).
- Improved screenshot support.
- Improved CSS tools.
Read Nate Dillon's full review
January 20, 2020
Score 9 out of 10
- CSS edits. The ability to change the style of dom elements and see the effect those changes have in real time without having to switch to your editor, make the changes, and reload the browser window saves a lot of time.
- The network tab is also a life saver for inspecting what assets are being loaded on the page and in what order they load, how long they take to load etc...
- It would be nice in the elements panel, if clicking on a node scrolled the screen to that node. On some large pages its easy to get lost in the code and not know where the element you're inspecting resides on the screen.
- It would be nice if, in addition to the console, there was a panel that behaved more like an editor instead of a command prompt. It may seem trivial but it would be very helpful when writing multi-line functions.
Read this authenticated review
Chrome DevTools are well suited for any front-end project and should be utilized by everyone who does web development. It provides a massive amount of functionality and gives the developer the ability to control the page at a very granular level.
October 23, 2019
Our whole organization uses Chrome DevTools to work on the front end of the web apps.
- If you want to play with styles and CSS, you can do that on the fly.
- Network tab provides detailed information about the http requests.
- I don't have any complaints
Read this authenticated review
- Being integrated with the browser, DevTools lets me access elements of the loaded page easily and directly. I can see what my page looks like in the browser while I fiddle with various parameters directly in the page through DevTools.
- DevTools lets me identify all of the artifacts that are loaded by the current page (images, scripts, media, etc.). I can easily determine if some third party package is getting in the way of my own content loading correctly.
- The Network tab gives me visibility into what the page is doing "behind the scenes". This is very helpful when working with dynamic content as I can see where and how things are loaded.
- While Chrome DevTools has a good REST sniffer, allowing me to see REST requests that my web app is making, it does not provide a general interface for constructing REST requests. I would like to see some functionality similar to Postman integrated with DevTools.
- While the Security tab allows visibility of the certificate associated with the site itself, it could present more information about the certificate and protocols in use. I would like to see full details of the entire certificate chain.
- Some items (such as Network conditions, Sensors, etc.) in the More Tools menu could be expanded upon.
- I would like to be able to connect to some external tools. It would be nice, for example, to be able to easily see traceroute (or mtr) output directly in the interface. I realize that some of these capabilities require elevated privileges, but that could probably be worked around be forking off a terminal instance to run the tool with Sudo or something similar.
Read Jan Peterson's full review
Given that DevTools is always available, it is well suited to impromptu inspections and investigations. It is less useful for automated testing where running Chrome may be more difficult (in a headless environment, for example). It would be nice to see some type of headless interface to DevTools where it could be accessed via some type of external API.
June 19, 2019
I used Chrome DevTools pretty regularly to sneak a look at the code of a webpage, either to do web development, or more likely nowadays, because I'm doing some data analysis and need to figure out how to scrape the data off the page and into R. Because it's baked right into Chrome, my regular browser, it's only ever a quick whack of F12 away.
- The selection widget is particularly handy--I can quickly and easily see how an element on a page fits in the page's structure
- Being able to edit CSS rules on the fly is great--that way I can see what's actually going to happen.
- It's also nice to be able to poke around in the Computed tab and see how an element's box model attributes are currently assigned and what will happen if I adjust, for example, the padding.
- I really miss Firebug's box model tools, which worked a bit more intuitively.
- The Console is handy, but can be hard to work with.
- I really wish there were a few more tools for outlining block elements and a color picker.
Read Jake Tolbert's full review
February 01, 2019
Our entire web development team uses Chrome DevTools on a daily basis. It complements similar tools by other major browsers but is the go-to tool of choice for looking under the front-end hood of a website under development. In the hands of a knowledgeable user, DevTools opens the door to a wealth of helpful information, debugging tools, and even skill-building.
- Provides clear, easy to understand, and actionable intelligence on how the browser is retrieving, parsing and rendering the page.
- Continuously incorporates new tools and helpful features. With nearly every major Chrome release there is a "What's new" update with at least one or two useful items.
- As one delves into DevTools, one encounters a gradually steeper learning curve. You can do a lot very quickly, but to fully utilize DevTools takes time as one explores what it can do.
- With many new updates, tools and items are moved, and a comfortable workflow becomes a frustrating search. This often happens when following only slightly outdated tutorials on a given feature, even in Google's own documentation.
- The experimental flags, settings, and options are scattered about and a little clunky to configure when one has to make changes in multiple places.
Read Taylor Morgan's full review
Web application testing and troubleshooting are one of the most time-consuming areas of a software engineer's tasks and the availability of reliable and comprehensive tools to facilitate this important job is critical. Chrome DevTools is an important tool in any developer's arsenal and it has been one of my long-time go-tos for this purpose. DevTools can reveal important information to you about errors your code is throwing, the state of your document model (the elements of your web page and how they are laid out) and the factors that are affecting the performance of your application. In my organization, we use Chrome DevTools across our engineering team to troubleshoot and test all of our front-end application code.
- Excellent DOM inspection tool that gives you important insights into your styles and element behavior, and allows you to make changes in-line that can show you what impact they will have if applied to your code.
- Outstanding tools for observing network and application performance, including throttling to simulate varying network speeds.
- A fantastic device emulator that allows you to view how your pages and application views will appear when viewed on a wide array of mobile devices such as tablets and smartphones.
- Debugging tools that give you the power to insert breakpoints to pause code execution and view the value of your code variables.
- It could really use an easier way to separate the kind of errors being logged to the console, such as network, security and CSS errors. This becomes a more acute problem when you consider that Firefox does have this feature.
- Unlike the Firefox and Edge dev tools, it forces you to click into a line item for network request in order to view the details of that request.
- Its performance measuring tool could stand to catch up to that of Microsoft Edge, which currently displays visualizations that are a bit easier to review.
Read Joel Tanzi's full review
If you are developing, testing or debugging web applications, then it would be hard to make a case against relying heavily on Chrome DevTools to help you along. It has kept pace with the development of other browser tools with similar features (Firefox and Microsoft Edge come to mind) and while it doesn't stand out as especially strong compared with the competition it remains a popular choice among developers and will likely be so for the foreseeable future. While it is a good idea to test across browsers and make use of their development tools as well, it is a strong choice for your default option.
September 01, 2018
Score 8 out of 10
- It has a great tool to check a site's assets loading, to see any loading errors, missing resources, redirections, etc.
- Their CSS editor is great to add new rules, update existing rules, etc. I like how you can see all applied changes in the website without refreshing the browser.
- I think the layout is too complex, it should be simpler and easy to use for an average developer.
- I would like more tools for CSS oriented development like Grid Helpers, Flux containers, CSS animations, etc.
- I would like a better tool for errors, like telling me what to do if I find a JS problem, CSS problem or a wrong redirection.
Read Miguel Useche's full review
When you find a JS bug in your web application, you can use Chrome to check its console for details, the JS editor to add new JS code or their CSS editor to add new rules to see if that solves your problem. You can do this without altering files and seeing results in real-time, so you don't have to lose time on saving and refreshing.
Also, you can use other tools to see if additional problems exist.
- First is the Debugging capabilities of Chrome DevTool i.e. very impressive you can set the break points where you think error might exist or you can simply go step by step until you encounter the issue.
- Second the capability of simulating mobile devices with device mode in Chrome DevTools - It is also great feature in which one can see where the network is throttling one can check for responsiveness of the view port on the mobile device.
- To analyse network performance - Generally it is a great feature to have because it lets us know which file it may be and if it's JS or CSS that is taking time to load or taking more resources then one can focus on them to make it light weight.
- As of now I don't have any issue with Chrome DevTool, it is best and improving day by day but if they can they should improve the interface so that switching between different tabs becomes easy.
Read Rahul Kumar Singh's full review
Chrome DevTools is well-suited for debugging JS errors, for looking on network performance, simulating mobile devices, and remotely debugging mobile web.
April 12, 2018
Score 9 out of 10
I mainly use Chrome DevTools for making little tweaks to the CSS/HTML of the page and immediately see the result. In other cases, it is also used for debugging and speed tests.
- While designing or editing a webpage Chrome DevTools lets you easily make changes to your HTML/CSS and immediately show the result in your Chrome browser.
- In the console, Chrome DevTools, shows errors inside your page.
- The timeline in Chrome DevTools can be used for optimizing the speed of your website.
- There are many functions and this might be hard for starters.
- User interface could be improved
Read Christiaan Bollen's full review
- It is a great tool for improving your website.
- Making changes and immediately getting the result in the browser without having to upload anything to a web server.
- If you are looking for some of the used resources in the website you are viewing there is a handy overview in the sources tab.
Chrome DevTools Scorecard Summary
About Chrome DevTools
Chrome DevTools Technical Details