-
Enable
#enable-devtools-experiments
flag inchrome://flags
section. -
Open Chorme Devtools and check
Settings > Experiments > Allow extensions to load custom stylesheets
. -
Create the following four files in a dedicated folder.
3.1.
devtools.html
<html> <head></head> <body><script src="devtools.js"></script></body> </html>
3.2.
devtools.js
var x = new XMLHttpRequest(); x.open('GET', 'style.css'); x.onload = function() { chrome.devtools.panels.applyStyleSheet(x.responseText); }; x.send();
3.3.
style.css
body.platform-windows, body.platform-linux, :host-context(.platform-windows), :host-context(.platform-linux) { --monospace-font-size: 12px !important; --monospace-font-family: "Consolas", monospace !important; --source-code-font-size: 12px !important; --source-code-font-family: "Consolas", monospace !important; } .monospace { font-size: var(--monospace-font-size); font-family: var(--monospace-font-family); } .source-code { font-size: var(--source-code-font-size); font-family: var(--source-code-font-family); }
3.4.
manifest.json
{ "name": "Custom Chrome Devtools Theme", "version": "1.0.0", "description": "A customized theme for Chrome Devtools.", "devtools_page": "devtools.html", "manifest_version": 3 }
-
Open Chrome Extensions tab, click
Load expanded extension
and point to the folder containing all four files.
-
-
Save vbsessa/e337d0add70a71861b8c580d5e16996e to your computer and use it in GitHub Desktop.
Hello to all
Do not tell me how to change the font size in the menu in devtools?
What's your OS?
In Linux, just add this to your style.css
:
.platform-linux {
font-family: 'Your font here', sans-serif !important;
font-size: 'Your size here' !important; /* optional */
}
Linux default is font-family: Roboto, Ubuntu, Arial, sans-serif;
For other, just replace the word linux
everywhere in style.css
by mac
or windows
according to your platform.
This is excellent! I set this up in my Mac (running Mojave) and it works perfectly.
Is there any resource available for changing other fonts sizes in Chrome DevTools (e.g., the console window)? The inspect window and source text are much better, but my console log still makes me squint and/or lean forward...Sorry, i haven't tried this kind of change yet. If you find it out, message me and i'll update the tutorial.
For me, it works to prepend body
to make the selector more specific. For example,
:host-context(.platform-linux) .monospace,
:host-context(.platform-linux) .source-code,
body.platform-linux .monospace,
body.platform-linux .source-code {
font-size: 12px !important;
font-family: Source Code Pro Semibold, monospace !important;
}
I was using some custom devtool extension but it wasn't effecting on console text. Now it works just fine. Thank you.
@eltriplet @abrhambas01
I took a quick look and it doesn't look like the width of these tabs is fixed in the css. They should grow according to the content. You could force a min-width or auto. Something like this:
.tabbed-pane-header-tab {
min-width: 80px !important;
width: auto !important;
font-family: Arial !important;
}
Quick tip: to find out which class to modify, open a console (floating mode) on top of another console (floating mode) and inspect the elements in the same way that you would with a web page.
Hope this helps.
It has worked out nicely, thanks .
I have used this styles, no buttons dissapear.
:host-context(.platform-linux) .monospace,
:host-context(.platform-linux) .source-code,
.platform-linux .monospace,
.platform-linux .source-code {
font-size: 11px ;
font-family: 'DM Mono', monospace ;
}
.platform-linux {
font-family: 'SF Pro Text', sans-serif !important;
font-size: 12px ; /* optional */
}
.monospace,
.source-code {
font-size: 11px ;
font-family: 'DM Mono', monospace ;
}
::shadow .monospace,
::shadow .source-code {
font-size: 11px ;
font-family: 'DM Mono', monospace ;
}
Does DevTools support ligatures? I'd like to use Fira Code.
wich is the default fon of devtool used to dender the html code...??.??
Does DevTools support ligatures? I'd like to use Fira Code.
I don't know, i've never tried a such type of font. Google it...
wich is the default fon of devtool used to dender the html code...??.??
I think it uses the 'monospaced' font defined in your OS.
I do not think so; I am investigating because it happens that the devtool html code viewer works correctly but when I try to use monospace in a web rendering ... the characters gain or lose space and everything is out of square ...
i find this in a spanish forum:
Hi,
I use Google chrome Version 98.0.4758.102 (Official Build) (64-bit) on Linux, and the above .css file does not switch the monospace/source code font everywhere in Chrome devtools, e. g. in the "Sources" tab, or in the "Computed" layout tab when examining CSS.
I had to add something like below to your current .css content in order to make this work:
.platform-linux, :host-context(.platform-linux) {
--monospace-font-size: 11px !important;
--monospace-font-family: <mypreferredfont>, monospace !important;
--source-code-font-size: 11px !important;
--source-code-font-family: <mypreferredfont>, monospace !important;
}
Maybe something to look into.
Thanks
Looks like !important
is not necessary when overriding these CSS vars:
.platform-mac,
:host-context(.platform-mac) {
--monospace-font-family: "SF Mono", Monaco, Consolas, monospace;
--source-code-font-family: "SF Mono", Monaco, Consolas, monospace;
}
@eltriplet @abrhambas01
I took a quick look and it doesn't look like the width of these tabs is fixed in the css. They should grow according to the content. You could force a min-width or auto. Something like this:
.tabbed-pane-header-tab { min-width: 80px !important; width: auto !important; font-family: Arial !important; }Quick tip: to find out which class to modify, open a console (floating mode) on top of another console (floating mode) and inspect the elements in the same way that you would with a web page.
Hope this helps.
great work, thank you.
But I fail to inspect the console UI 🤣
If you guys want to customize other stuff, please read the official source code below
But I fail to inspect the console UI
I think your devtools window should be in floating mode in order to be inspected.
to use fira code
@import url('https://fonts.googleapis.com/css2?family=Fira+Code:wght@300;400;500;600;700&display=swap');
font-family: 'Fira Code', monospace;
@chrillep - Thank you. Only saw this now.
When I use Chrome 123 there are #enable-devtools-experiments flag. any other way?
Thanks @vbsessa !
It works for me on Chromium ver.124.0.6367.60 - Ubuntu Linux & Chrome ver.124.0.6367.78 - Windows. (I have no bootable Mac.)
style.css
body {
font-size: 13px !important;
font-family: "Myrica M", Inconsolata !important;
}
.platform-windows, :host-context(.platform-windows) {
--default-font-size: 13px !important;
--default-font-family: "Myrica M", Inconsolata !important;
--monospace-font-size: 13px !important;
--monospace-font-family: "Myrica M", Inconsolata !important;
--source-code-font-size: 13px !important;
--source-code-font-family: "Myrica M", Inconsolata !important;
}
.platform-linux, :host-context(.platform-linux) {
--default-font-size: 13px !important;
--default-font-family: "Myrica M", Inconsolata !important;
--monospace-font-size: 13px !important;
--monospace-font-family: "Myrica M", Inconsolata !important;
--source-code-font-size: 13px !important;
--source-code-font-family: "Myrica M", Inconsolata !important;
}
How to update this to use Manifest 3? This is now throwing error: "Manifest version 2 is deprecated, and support will be removed in 2024. See https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline for details."
Accepted manifest.json
with no error
{
"name": "Custom Chrome Devtools Theme",
"version": "1.0.0",
"description": "A customized theme for Chrome Devtools.",
"devtools_page": "devtools.html",
"manifest_version": 3
}
Updated.
Thanks to @3otis.
Updated the CSS and also created a repository with all files.
https://github.com/vbsessa/chrome-devtools
Dropped mac support for now.
If someone uses a mac, could please share which class is being used by chrome? Using .platform-mac
is breaking things, at least for me.
Still working. Tried out on Fedora 40.
Thanks. Hero.
Sorry, i haven't tried this kind of change yet. If you find it out, message me and i'll update the tutorial.