Most if not all functions that extensions could provide to headless chrome can be realized via the DevTools API that headless exposes to its users.

(This also renders headless chrome unsuitable for testing chrome extensions.) So even if we solved (2), most existing extensions would not be compatible. Changing this requires a lot of refactoring that doesn't seem justified given the benefit we'd gain.Įither way, extensions would likely have to be adapted to work with headless chrome due to (1).Of the APIs we could feasibly support, only parts are implemented in such a way that we can currently reuse them for headless chrome.A lot of extension APIs are specific to non-headless browsers, so can't be supported in headless chrome.You can find the complete analysis in Add extension support for headless in his comment mentioned the real time issues as: We've decided against implementing extension support in headless mode for now because supporting all the required features is rather complex No, google-chrome in headless mode doesn't supports extensions in his comment clearly mentioned:

Fun google chrome extensions