I don't wish to disable my extensions – after all they're there for development purposes – but I want to disable their output from the console in Web Inspector. Is there a way to do this?

N.B. a very similar question has been asked on StackOverflow, but it seems that question and its answers are leaning towards disabling extensions, which is not what I want (since I obviously use them for development) – I simply want to suppress their output from the console.

enter image description here

  • 1
    6 year later and they refuse to fix this issue, best you can do is set a filter each time you load devtools – nodws Aug 17 '18 at 20:00

Firefox has a way to change the console logging level for specific extensions from about:config.

Chrome doesn’t have this capability. Your options:

  1. Filter out all messages from a particular source file by right-clicking the white (blank) part of console message line and choosing Filter > Hide Messages from foo.js. You can undo this filtering from the same menu later, if you wish. Chrome will remember to do this filtering for you until you disable it (even if you navigate somewhere else or restart Chrome).
  2. Override one or more console methods. This approach only affects the current scripting context. Chrome extensions run in their own isolated worlds with their own window objects, global scopes, and console objects. If you can’t edit the source code of the extension, you’ll need to paste and run your console-altering scripts in each extension’s execution context, and your modifications will only be in effect until the page is unloaded. You can change the console’s effective execution context using the dropdown at the bottom of the console that says <page context>. Note that any frames or iframes in the page also have their own execution contexts, accessible using the frame dropdown (initially set to <top frame>).

Just temporarily disable the extensions.

This will add a button to your browser and it will only require two clicks to toggle your extensions.

  • 1
    That's a nice tip (thanks!), however if you prefer to use the extensions while developing, it's awkward having to disable them just to get a clean console. – Henrik Jun 8 '12 at 1:04
  • 1
    @hced: Another approach which might work is running in incognito mode and allow the extensions you need for developing in incognito. Yet another approach is creating a separate user profile for developing. From your screenshot it only appear to be two bad extensions, perhaps you can just disable those and/or find alternatives. In any case, a lot of options to try; and if you really want it, raise a feature request at Google Chrome and hopefully one day it'll be available for all developers... – Tom Wijsman Jun 8 '12 at 1:42
  • This is not a solution. I am on jsfiddle, programming at night. I want my high-contrast extension to invert the colors, but I don't want to see its output. There are other examples too. There really should be a way to suppress just the console ouput.... – Jonah May 29 '13 at 11:09
  • @Jonah: Correct your extension to not output to the console. – Tom Wijsman May 29 '13 at 14:42

This is currently not possible, but there is an ongoing feature request for it (or, rather, for the same problem happening on the Network inspector tab). "Star" it to help make it happen :)



Another approach is loading the window in cognito, which by default ignores your extensions

Press (cmd or ctrl) + shift + n to load a private browsing session.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.