How to record screen in Chrome, with nothing to install

You can record screen in Chrome without installing anything. The browser has offered the underlying capture API for years, and any web page can use it to request a live video of a tab, a window or the whole display. The catch is that the built-in picker is only the engine. What you end up with depends on three decisions most people make without thinking: which surface you share, whether you capture the audio you need, and what your screen looks like before the recording starts.

The same failure shows up constantly. Someone records a product walkthrough by sharing an entire 2560 by 1440 display, then wonders why the video is hard to read on a laptop. The browser’s interface shrinks to a sliver of the frame, the cursor is a speck, and the one button that matters sits in a corner of a picture that’s mostly empty desktop. The recording technically worked. The choice of what to share made it unwatchable.

This guide covers how browser recording actually works, how to choose a capture surface, how to get audio without an echo, and where the approach runs out. If you only need the short version, skip to the end, but the middle sections are where the difference between a clean file and a frustrating one is decided.

What Chrome hands the recording page

When a page wants to record your screen, it asks the browser for a video stream. Chrome then shows its own picker, a list of tabs, windows and screens you can share. The page never sees your desktop directly. It receives only what you selected, as a live stream, and it can pass that stream to a recorder that encodes it into a file.

That design explains most of what you’ll notice in practice. Three consequences matter more than the rest.

The recording is only as good as the surface you picked. A single tab gives the recorder that tab’s contents and nothing else. The entire screen gives it everything on that display, including the notification that slides in with a client’s name in it and the chat window you forgot to minimize.

The recording lasts as long as the sharing does. Stop sharing from Chrome’s sharing bar, navigate the captured tab somewhere else, or close the page that runs the recorder, and the stream ends. A recorder that lives in a browser tab stops when that tab does, so leave it open and leave it alone for the whole take. A stray keyboard shortcut that closes the wrong tab is enough to end a long session, so treat the recording page like a camera that someone is standing next to.

The page and the picker share control. A recording page can pre-select a pane, such as the Chrome Tab or Window option, but it cannot choose a specific window for you. That restriction is deliberate, so a web page can’t quietly grab something you didn’t mean to share. Pages can also offer a “Share this tab instead” control so you can swap the captured tab in the middle of a session. Whether you get that depends on how the page was built, not on Chrome alone.

Choose the capture surface before you press record

The picker has three panes, and they look similar enough that people pick the wrong one. They produce very different files, and the difference shows up only when you watch the result on a smaller screen.

For browser work I default to the tab, and the reason is resolution rather than convenience. A tab capture reflects the size of the tab’s viewport. If you size the window to your target output and set the zoom, the recording is composed at the size you’ll deliver. An entire-screen capture takes a 2560-pixel display and asks the recorder to shrink it to a 1920-pixel or 1280-pixel output, so every label on the page gets smaller. The interface you were trying to show becomes the thing your viewer squints at.

Think about it with numbers. Say a settings label is 14 pixels tall at the zoom you’re using on a 2560-wide display. Scaled into a 1280-wide export, that label is roughly 7 pixels tall. That’s the difference between readable and decorative, and it’s why an entire-screen recording of a web app looks fine on a 27-inch monitor and falls apart on a phone.

Two more details trip people up. The tab capture excludes the browser’s own interface, meaning the address bar and the tab strip. If the URL matters to the story, use a window or the entire screen, or show the address in the page itself. And many recording pages hide their own tab from the picker by default, so if the tab you want is missing, check whether you’re looking at the recorder’s tab, which can’t be recorded from inside itself.

Get audio that doesn’t echo

Two sources of sound need two separate settings, and mixing them up is the most common audio mistake people make.

Tab audio is whatever the captured tab is playing: a demo video embedded in a page, a sound effect in an app, a clip you’re showing the viewer. In the Chrome Tab pane there’s a checkbox to include it. If you don’t tick it, the tab’s sound is simply absent from the file, even though you can hear it perfectly well on your own speakers.

Your voice comes from the microphone. The recording page asks for microphone permission separately, and Chrome does not mix your narration into the tab-audio track. If the right microphone isn’t selected in the recorder, your narration isn’t there, and you won’t notice until you play the file back. Check the microphone level in the recorder before every session, not just the first time you set it up, because laptops and headsets switch inputs without asking.

The failure case is the loop. Suppose you record tab audio while the tab plays through your speakers and the microphone is open. The microphone hears those speakers, and the recording carries a second copy of the playback a fraction of a second behind the original. On a short clip it sounds like a faint slap-back. On a ten-minute tutorial it’s exhausting, and it’s very hard to remove in an editor afterward without damaging the voice.

How to record screen in Chrome: a walkthrough for a web app

Here’s the sequence I’d follow for a recording of a browser-based product. Each step is quick, but the first one matters most, because it decides how the rest of the take looks.

1. Set the window before the recording exists. Size the browser window to your target output. Set the browser zoom so the interface reads comfortably at that size. For demos, 110 to 125 percent is a sensible starting point, but the right number depends on your output and your product’s density. Hide the bookmarks bar, close unrelated tabs, and sign in to a demo account with realistic but invented data rather than a real customer’s workspace.
2. Open the recorder, then choose the tab. Select the Chrome Tab pane, pick the app’s tab, and tick the tab audio box if the app plays sound you want in the file. Then confirm the microphone in the recorder’s own settings, not just in the operating system, because the recorder may be using a different input.
3. Record ten seconds and check the file. Stop, open the result, and check three things. Is the smallest label readable at phone size? Can you see the cursor on each click? Does your voice sound like you in a room, or like something bouncing off a wall? If any answer is no, fix it now. A ten-second test costs you a minute, and a failed twenty-minute take costs you the afternoon.
4. Record each section as its own take. Don’t run one long recording for a ten-minute tutorial. Short takes are easier to redo, and a stumble in minute six won’t force you to re-record minutes one through five. Stop with the Stop sharing button on Chrome’s bar, then check the final second of the take. It’s often the cursor drifting toward the stop control, and you want that trimmed.

Zoom is the lever most people miss: browser zoom rescales the page, so every button and label gets larger in the capture without changing the resolution. Keep the same zoom across a whole series of videos, and the interface looks identical from one video to the next. That consistency is a big part of what makes a series look produced rather than improvised.

Notice what the walkthrough does not include. There’s no step for “make it look good,” because that happens in a different layer. Capture is about getting faithful, sharp, correctly-sized pixels and audio. Presentation is about where the viewer’s eye goes, and that’s a separate job with its own tools.

Where browser recording runs out

Browser recording is good enough for most software tutorials and product walkthroughs. It also has limits you should plan around instead of discovering mid-take.

It can only capture what the browser will share. Protected video, such as many streaming services that use digital rights management, shows up as a black rectangle where the video should be. If your demo depends on a streamed clip, record your own sample file instead, or plan a cutaway.

The entire screen is a privacy surface. Notifications, the dock or taskbar, a chat popup in the corner, a password manager dialog: all of it gets recorded if it’s on the display. Before any full-screen take, turn on focus mode, close unrelated applications, and look at the corners of the frame on a test recording. A notification that exposes a customer’s name is the kind of mistake you can’t cut out cleanly, and it can end up on a public help page.

Keep the captured tab in front. Switching away from a shared tab can cause stutter or dropped frames on some machines, particularly when the rest of the system is busy. If you need to check notes, use a second display or a separate window rather than alt-tabbing through the recording. A second monitor is the single cheapest upgrade for anyone who records regularly.

Test the cursor before a long session. Whether and how the cursor is drawn into the capture depends on the recording page’s settings, and results differ between recorders. A cursor that’s missing from the file is a quiet problem, because you may not notice until someone asks where the click happened. Ten seconds of testing catches it.

Finally, browser capture doesn’t know what you’re trying to show. It records faithfully, including the hesitation before the click, the page that’s still loading, and the three-second pause while you decide what to say. That’s not a flaw in the tool. It’s the reason the step after recording exists.

Make the file look edited, not just recorded

Everything above gets you a clean file. Making that file look finished is a second layer. Good tutorials zoom into each click, cut dead air, keep narration short, and show the viewer the next thing before they need to look for it. You can do all of that by hand in a video editor, frame by frame, which takes most people longer than the recording did. Or you can record with a tool that handles the zoom and cleanup as you go.

RecordlyPro takes the second route. It records in Chrome, Edge, Brave or Arc with nothing to install, adds auto-zoom on every click, applies cursor effects, and generates captions and chapters automatically. If you want to understand what click-following zoom is actually doing to the frame, how auto-zoom works in screen recording walks through it in detail.

The short version

Recording screen in Chrome is simple to start and easy to get wrong in ways you only see later. Share a single tab for browser work, size the window and the zoom before the take, use headphones whenever tab audio is on, and record ten seconds before you commit to anything long. Chrome handles the capture. Your setup decides whether the file looks like a finished video or a raw one.

If you’d rather skip the manual zoom and cleanup, record a walkthrough in your browser. Nothing needs installing, and the zoom, cursor effects, captions and chapters are added for you. You can also see how the steps fit together before you start. Pick one workflow you already do, record it once, and watch it back on your phone. Then change a single thing before the next take.

Keep reading

Playbook

Async video: stop scheduling the meeting you could record

A hundred random links can do less than five relevant ones. Here's what makes a backlink pass real ranking value in 2026 — and what makes it worthless or worse.

Sofia Meyer October 6, 20262 min read

Playbook

Auto-zoom in screen recordings: what it is and why your demos need it

A hundred random links can do less than five relevant ones. Here's what makes a backlink pass real ranking value in 2026 — and what makes it worthless or worse.

Sofia Meyer October 13, 20262 min read

Playbook

How to choose a screen recorder for product demos in 2026

A hundred random links can do less than five relevant ones. Here's what makes a backlink pass real ranking value in 2026 — and what makes it worthless or worse.

Sofia Meyer October 16, 20262 min read

Explainer

Dofollow vs nofollow in 2026: what still passes value

The link attributes changed, Google's treatment changed, and a lot of advice is out of date. Here's what dofollow, nofollow, sponsored and ugc actually do now.

The Recordly Team October 10, 20262 min read