Chrome guest profile: when a throwaway window is the right choice

A guest profile in Chrome is the option that sits at the bottom of the profile menu and gets used once a year, usually when someone else needs the machine for five minutes. It is a genuinely useful thing, and it is also the feature most often reached for when the actual need is something else. The confusion is understandable, because Chrome offers three arrangements that all produce a window with no trace of the previous session, and their differences only show up at the moment they matter. What follows sorts out which of the three answers which question.

What a guest window is, in Chrome's own terms

Google describes the purpose narrowly, and the narrowness is the point.

When you use a public computer or share a computer with others, websites that you visit in Guest mode won't appear in the browser history. Source: support.google.com

The second half of the description is the part that separates Guest from everything else in Chrome: in Guest mode, a person cannot find or change any other Chrome profile's information. A guest window is not a clean view of the current profile. It is a window with no profile behind it at all. Bookmarks from the signed-in profile are not there. Saved passwords are not there. There is nothing to sign out of, because nothing was signed in.

Opening one runs through the profile icon at the top right, then Open Guest profile. Closing it on macOS means selecting Close at the top left of the window, or going back to the profile menu and selecting Close guest. What happens at that moment is stated directly: browsing history, cookies, and site data are deleted.

The whole of the feature is in those two facts. Nothing comes in, and nothing goes out. That makes it excellent for exactly one situation and unsuitable for several situations it gets applied to.

Guest, Incognito, and a second profile

The three arrangements are easiest to tell apart by asking what each one starts from and what each one leaves behind.

	Guest profile	Incognito window	Second Chrome profile
Starts from	Nothing. No bookmarks, no passwords, no extensions from any profile	The current profile's bookmarks and settings	Its own bookmarks, history, passwords and settings
Can reach other profiles' data	No	Yes, it is the same profile	No, each profile is separate
Kept when the window closes	Nothing. History, cookies and site data are deleted	Bookmarks saved and files downloaded are kept. Site data and the record of sites visited are not	Everything, the same as a normal window
Third-party cookies	Follows the settings it was given	Blocked by default	Follows that profile's settings
Opened from	Profile icon, then Open Guest profile	Command, Shift and N	Profile icon, then the profile name

Two rows in that table do most of the work. The first row explains why a guest window feels awkward for personal use: nothing familiar is in it, by design. The third row explains why Incognito is not a substitute for a guest window on a shared machine: Incognito runs inside the current profile, so a person using it can still open the bookmark bar and see where the owner of the machine banks.

Google's wording on Incognito is precise about what survives. Chrome retains bookmarks that are saved and files that are downloaded when Incognito is exited, while site data and the record of sites visited are not retained after the session ends. During the session, cookies and site data are kept temporarily so that sites work at all, and removed when the session ends. Third-party cookies are blocked by default there, which is a real difference in behavior and occasionally the reason a site misbehaves in Incognito but not elsewhere.

The jobs a guest window does well

Handing the machine to another person is the case the feature was built for. They get a working browser, they cannot see anything belonging to the owner, and closing the window removes what they did. No account has to be signed out of first, and nothing has to be cleaned up afterwards.

Checking what a page looks like with nothing attached is the second case. A guest window carries no extensions, no signed-in state, and no accumulated cookies. That makes it a reasonable way to see a site as a first-time visitor sees it, or to work out whether a problem on a page is caused by something in the usual profile. Incognito is often used for this and is weaker at it, since it inherits the profile it was opened from.

A one-time sign-in that should not persist is the third. Logging into a service on a borrowed machine, or into a client's account that should not end up in a password manager, fits the shape of the feature exactly. The session ends when the window closes and there is nothing left to remove.

What connects all three is that the session is disposable and single. The moment a second disposable session has to exist at the same time, or the moment the session needs to come back tomorrow, the feature stops fitting.

Where a guest window is the wrong tool

The most common misuse is as a second account. Someone with two accounts on the same service opens a guest window for the second one, and it works, once. Then the guest window closes and the sign-in is gone, so tomorrow it has to be done again. Two-step verification has to be cleared again. Any per-account setting the site remembers through cookies is gone again.

Chrome's answer for this is a second profile, not a guest window. Adding one runs through the profile icon and Add Chrome profile, and each profile keeps its own bookmarks, history, passwords, and other settings. The cost is documented and should be read before experimenting, because it is not reversible: after a profile is removed from Chrome, that profile's bookmarks, history, passwords, and other settings are erased from the computer.

The second misuse is as a privacy measure on a person's own machine. A guest window deletes local traces, and that is all it does. Google's own guidance on the page is explicit that a device owner may be able to access what was done, and that websites, employers, networks, and internet service providers can still see the activity. The instruction that follows from that is also stated plainly: only log into sensitive websites on trusted devices.

The third misuse is as an organizing tool. Guest windows all look alike, they hold nothing between sessions, and there is no way to have several of them arranged for different purposes. Anyone reaching for Guest in order to keep two contexts apart during a working day is using a temporary feature for a permanent job.

What a guest window does not isolate

It is worth being specific about the limits, since the feature is often assumed to be stronger than it is.

A guest window does not hide activity from the network. That boundary is the same one Incognito carries, and Google's description of Incognito names the parties who can still observe it: the websites visited, including Google sites, and organizations that manage the network.

A guest window does not survive its own closing, which means it cannot hold a session that needs to exist tomorrow morning. It also does not carry extensions, so any workflow that depends on a password manager extension or a clipping tool will not function inside one.

And a guest window does not multiply. There is one, it is generic, and it has no memory. If the requirement is several sessions that each persist and each stay separate, the mechanism for that in Chrome is profiles, and the practical limit of profiles is not technical but human: each one is a separate Chrome window with its own Dock behavior, and keeping five of them straight during a working day is its own task. Keeping a set of web apps grouped and signed in separately without managing five browser windows by hand is what the Workspaces model is for, and it is a different question from the one Guest answers.

Telling which window is which

The failure mode with any of these arrangements is not technical. It is typing something into the wrong window. A guest window looks almost exactly like a normal one on macOS, and after a few minutes of use the distinction stops being visible.

The reliable check is the profile menu at the top right. In a guest window it offers Close guest, which is an option that does not exist anywhere else. In a normal window it shows the profile name and the list of other profiles. Anyone who works across several of these arrangements regularly should get into the habit of glancing there before signing in to anything, because the consequence of getting it wrong runs in both directions. A password typed into the wrong window can be saved to a profile it should not be in, and a session established in a guest window vanishes the moment it closes, which is a surprise if the window was assumed to be a normal one.

Profiles are easier to tell apart than Guest is, because Chrome allows a name, a photo, and a color scheme to be chosen when a profile is created. Those are not decoration. The color is the fastest way to know which session a window belongs to without reading anything, and on a machine running more than two profiles it is the difference between a workable arrangement and a guessing game.

What outlives the window anyway

The deletion list for a guest window is specific: browsing history, cookies, and site data. Things that are not on that list are not covered by it, and the most important of those is a downloaded file. A file written to the Downloads folder is a file on disk, and closing the window does not remove it. Google is explicit about the equivalent case for Incognito, stating that Chrome retains bookmarks that are saved and files that are downloaded when Incognito is exited.

This matters when a guest window is being used to look at something that should not be left behind. Anything opened and read in the browser is covered by the deletion. Anything saved, exported, or downloaded to look at in another application is not, and has to be removed by hand from the Downloads folder.

The same logic applies to anything the visitor did outside the browser. A guest window is a Chrome feature, not a macOS one. It does not affect what other applications recorded, what the system clipboard still holds, or what a screenshot saved to the desktop. Treating it as a clean-machine feature rather than a clean-browser feature is the overestimate worth avoiding.

Deciding in one pass

Three questions settle it.

Is another person about to use this machine? Use a guest window. It is the only one of the three that keeps the current profile's bookmarks and passwords out of reach.

Does the session need to exist again tomorrow? Do not use a guest window. Use a second profile, and accept that removing it later erases what it holds.

Is the aim to be unobserved rather than to leave no local trace? Neither Guest nor Incognito does that, and the pages describing both say so directly.

What to change first

Stop using Incognito for the shared-machine case and use Open Guest profile instead, since Incognito leaves the current profile's bookmarks and saved passwords reachable. If the reason for reaching at Guest was to keep two accounts or two contexts running side by side every day, that is a profile problem rather than a privacy one, and a browser that keeps each web app and each account in its own pane, as SpaceDeck does, addresses it without a window per account.