Close Menu
    Facebook X (Twitter) Instagram
    • About
    • Privacy Policy
    • Write For Us
    • Newsletter
    • Contact
    Instagram
    About ChromebooksAbout Chromebooks
    • News
      • Stats
    • AI
    • How to
      • DevOps
      • IP Address
    • Apps
    • Business
    • Q&A
      • Opinion
    • Gaming
      • Google Games
    • Blog
    • Podcast
    • Contact
    About ChromebooksAbout Chromebooks
    News

    How Google will speed up the Lacros browser on Chromebooks

    Kevin TofelBy Kevin TofelJuly 25, 2022Updated:September 2, 2025No Comments3 Mins Read
    Share
    Facebook Twitter LinkedIn Pinterest

    A few months back, I mentioned that I’m using the Lacros browser full-time. Lacos is essentially the Linux version of the Chrome browser and is part of Google’s effort to decouple Chrome from ChromeOS. Today I found code that will eliminate one of my pain points using Lacros. Google intends to speed up the Lacros browser on Chromebooks so it starts quicker.

    Why is this a pain point for me? To understand that, you need to understand how Google is implementing the Linux version of Chrome on Chromebooks.

    Linux on Chromebook containers
    Linux containers on a Chromebook

    Unlike the native browser in ChromeOS that we’ve had since the first Chromebooks in 2010. Lacros is, as mentioned, written to run on native Linux. And Google is beefing up the security of this browser by running it in a container, or a separate sandbox, from all other apps. This is the exact same approach Google uses to enable Linux on Chromebooks. And that works quite well.

    Here’s the problem: It takes time for a Chromebook to fire up that container. More so on entry-level hardware than on the wicked fast HP Elite Dragonfly Chromebook with its 12th gen Intel CPU. Even on that device, though, it’s an issue.

    When I open the Lacros browser on my Chromebook, it take a few seconds before I can actually see or use it.

    Lacros vs ChromeOS browser on Chromebooks
    Chrome browser on the left, Lacros browser on the right

    So how is Google going to fix this and speed up Lacros?

    The solution is quite simple, even if the coding to make it happen isn’t. As soon as you boot up your Chromebook and the login screen appears, Google will start the Lacros container in the background. The idea is that in the few seconds it takes you to type your password on PIN, the Lacros startup on Chromebooks will already be happening.

    Of course, there will be a transition from Chromebooks using the Chrome browser to using Lacros. And during that time, if you don’t have Lacros enabled on your device, the container will simply shut down, hopefully before the login process completes. You’d then just click your Chrome browser icon and be none the wiser.

    Lacros startup on Chromebooks

    This approach is actually no different from how Google enables Android apps upon bootup. In fact, that caused some issues for people who don’t use Android apps. Google resolved that by lowering the priority for the Android container startup process unless you actively try to open an Android app.

    I don’t yet see the experimental flag to start Lacros upon bootup on my Chromebook with the ChromeOS 105 Dev Channel. Hopefully, it arrives in the next ChromeOS update so I’m not waiting two or three seconds between opening my browser and actually using my browser.

    Chrome browser Chrome OS Chromebooks ChromeOS Experimental Features Flags Lacros browser
    Share. Facebook Twitter Pinterest LinkedIn Tumblr
    Kevin Tofel
    • Website

    After spending 15 years in IT at Fortune 100 companies, Kevin turned a hobby into a career and began covering mobile technology in 2003. He writes daily on the industry and has co-hosted the weekly MobileTechRoundup podcast since 2006. His writing has appeared in print (The New York Times, PC Magazine and PC World) and he has been featured on NBC News in Philadelphia.

    Related Posts

    AI Tools With Shortest User Loyalty In 2025

    August 25, 2025

    Is Janitor AI Down?

    August 21, 2025

    Why Meta Quest 4 Could Be the Next Big Thing in VR?

    August 11, 2025

    Comments are closed.

    Best of AI

    Most Repetitive AI Prompts Ever Entered Into Chatbots (2025)

    August 20, 2025

    Which AI Chatbots Are Most Trusted to Handle Sensitive Data? (2025)

    August 15, 2025

    Most Common AI Tools Used at Work (And What They’re Replacing) 2025

    August 11, 2025

    Which AI Chatbot is Used Most by Students?

    August 7, 2025

    Perplexity Statistics And User Trends [2025 Updated]

    July 29, 2025
    Trending Stats

    Average Chrome Tab Lifespan Statistics (2025)

    September 3, 2025

    Which Chrome Permissions Are Most Frequently Revoked After Being Allowed? (2025)

    September 2, 2025

    Chrome Usage vs. Focus Apps Statistics [2025 Updated]

    August 29, 2025

    How Many Chrome Extensions Does the Average User Have – But Never Use? (2025)

    August 27, 2025

    Chrome Mobile Market Share Statistics (2025 Updated)

    August 23, 2025
    • About
    • Write For Us
    • Contact
    • Privacy Policy
    • Sitemap
    © 2025 About Chrome Books. All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.