One of the cool things about Chrome is that we're able to play with experimental features. That means we can install beta or even alpha versions, but we can also try some of the truly experimental things that haven't been included on even the most alpha of alpha builds through what are called "flags."
Let's have a look at what they are and how to get started breaking things.
What are Chrome Flags?
Flags are experimental features as well as features most users will not need that are buried in a place where they won't be accidentally enabled.
Some are features Google is working on implementing, some are just things being tested to know if it even should work on making a stable feature, and some are there because some obscure use case means there needs to be a way to do a thing.
Experimental things are cool when they are cool, but not so much when they aren't.
Flags can improve your experience using Chrome or make it worse — that's how things go with anything still in its experimental phase. They can also let you have access to content that you wouldn't normally be able to see or use, like VR websites or features in other Google products like YouTube that aren't quite yet ready for the general public.
They can also change the way Chrome itself runs by changing settings for hardware acceleration or memory management which can lead to problems. These problems can be simple and solved by reverting a setting or significantly worse. I've never heard of someone ruining a computer by changing a Flag, but there's a first time for everything so you need to be careful.
Most people probably aren't interested in changing any Chrome Flags and that's probably for the best. But if you're the type who can't leave well enough alone, Chrome has you covered.
How to access Chrome's Flags
To change any Flags, you need to know where they are. They aren't exactly out in the open, but thankfully they also aren't hard to uncover. Whether you are using a Chromebook or Chrome on another computer or even Chrome on your phone, you get to them the same way.
- In the Omnibox (Chrome's address bar) on a blank tab, type the following: chrome://flags/
You'll be greeted with a message warning you that these can experimental settings, and that things can go horribly wrong. And it's true — you can make Chrome unusable if you change the wrong thing, and you can do worse things, too. This is more than Google covering themselves in case you break something, and it's a warning you should pay attention to.
At the top of the page, you'll see a search box where you can look for a specific Flag that someone or a website might have told you about. Google is pretty good at search.
You'll also see a list of the Flags themselves. Each entry has a short description of what the setting changes, a button to enable or disable the Flag and a hyperlink so that you can get to that flag through the Omnibox without searching, such as chrome://flags/#WebRtcUseEchoCanceller3 which takes you to the Flag that attempts to cut back on microphone echo during web real-time chat instances. This is a good example of a Flag that won't harm anything if you want to try it.
There's always a way to go back unless you change a Flag that takes the reset button away!
To change a Flag, click or tap the button in its listing. you'll see three choices: Default, Enable and Disable. Enable and Disable are simple enough to understand, but Default may throw you. it simply means that you want the setting to go back to whatever it was before you started changing things. it's handy because it means you don't have to remember if you enabled it or disabled it.
The most important button is at the very top of the page next to the search box: Reset all to default. That's your get out of jail free card and as long as you can still start Chrome and get to it, you'll be able to go back to where you were before you broke anything.
Should you change any Flags?
Ahh. That's the meat of it all, isn't it? These experimental things are right there and we get to try them as we please, knowing the risks involved. And as long as you understand those risks — you could lose browser data or compromise your security or privacy — there's nothing wrong with trying things.
You'll see tips about changing Flags online whenever someone finds a good one, but you probably shouldn't just start jamming on buttons just because you can. An example of a Flag you might have heard about was the QUIC Flag — chrome://flags/#enable-quic. QUIC is Google's experimental protocol, and it stands for Quick UDP Internet Connection. Its goal is to provide secure web browsing faster than the existing TLS/SSL protocols and in some ways, it's pretty good. One way that it isn't so good is that most Mitmproxy servers are unable to filter websites that serve you pages using QUIC. If you need to use a mitmproxy (you would know if you did) you can disable the QUIC Flag so it's never used and every site serves you using TSL/SSL.
Never change a Flag for something you don't understand. Trust me because I push buttons before I read them.
Another Flag that you can safely play with is the Fast Tab Unloader, chrome://flags/#enable-fast-unload. It's Disabled by default on Chrome stable and what it does is allow the browser to run the process that checks, saves any data if needed, then closes the tab in its own thread outside of the user interface. The tab "closes" right away even though it's still being handled in the background.
Of course, there are a lot of other Flags that can make everything worse, which are the ones you need to look out for. I'm not going to start talking about the ones I've tried and made everything worse other than to say Web Assembly Flags will break your browser and NaCI plugin Flags are things you should know what they are before you just press buttons. Trust a person who just pushed buttons and was sorry.