How to Compare Two Files in VS Code (Built-In Diff, No Extension)

Two files, a few hundred lines each, and the one change that actually matters is buried somewhere in there. Scanning both files by eye wastes time nobody has to spare.

Learning how to compare two files in VS Code turns that guessing game into a side by side view where every added, removed, and modified line gets marked in color. Two clicks and you’re looking straight at it.

Visual Studio Code already sits on most developer machines at this point. Stack Overflow’s 2025 Developer Survey found 75.9% of developers use it regularly, its fourth year running as the most used code editor.

The diff editor ships built in, so there’s nothing to install first. Right click two files in the Explorer and VS Code renders the differences instantly. Same goes for a file checked against its own git history, or a quick comparison run straight from a terminal.

What Is File Comparison in VSCode

Microsoft built this straight into the editor, so there’s no extension required for a basic file diff. That alone puts it ahead of a lot of comparison tools people assume need a plugin first.

Two versions of a file land side by side, and every differing line gets marked. That’s really the whole feature, at least at the surface level.

If you’re still getting oriented with what VS Code actually is beyond a plain text editor, the diff editor is one of the more used built-in tools it ships with, right up there with the integrated terminal.

There’s a handful of reasons this gets used day to day, and they’re not all the same kind of task. Reviewing a teammate’s changes as part of a structured code review process is one. Spotting an accidental edit before it gets committed is another, and so is tracking what changed between two versions of a config file, line by line. Resolving a merge conflict before it blocks a pull request rounds it out.

Comparing two standalone files isn’t quite the same thing as comparing a file against its own version history inside a git repository, even though both lean on the same diff editor under the hood. Only the source of that second version changes.

Teams lean on this for ongoing change tracking just as much as one-off checks, especially on files that pass through a few different hands before anything ships.

How to Compare Two Files Using the Explorer Right-Click Method

Right clicking two files inside the Explorer pane is the fastest way into a diff, assuming both files already sit inside your open workspace folder.

Select the first file, choose Select for Compare, then right click the second file and choose Compare with Selected. Broken into steps, it looks like this.

1. Open the folder containing both files (File > Open Folder)
2. Right-click the first file and select Select for Compare
3. Right-click the second file and select Compare with Selected
4. VS Code opens both files in the diff editor automatically

There’s a faster version of this when both files sit in the same folder view already. Hold Ctrl on Windows and Linux (or Cmd on macOS), click both files, right click the selection, and choose Compare Selected.

One thing to know before you go looking for this option on a file that isn’t showing it. This method only works when both files are visible inside an open workspace folder. Anything sitting outside the current folder needs the Command Palette method instead.

How to Compare Two Files Using the Command Palette

The Command Palette exposes basically every VS Code command by name, file comparison included, through one keyboard driven menu.

Press Ctrl+Shift+P on Windows and Linux, or Cmd+Shift+P on macOS, and it opens from wherever you are in the editor.

Here’s how that one works.

1. Open the first file as the active editor tab
2. Open the Command Palette and run File: Compare Active File With…
3. Pick the second file from the picker that appears

Nothing’s bound to this one by default, no keyboard shortcut at all. Anyone who compares files often enough to care usually adds one through their own VS Code settings, under keyboard shortcuts.

Comparing an Open File Against the Clipboard

Run File: Compare Active File with Clipboard and it diffs the open file against whatever’s currently copied.

Default shortcut is Ctrl+K C on Windows and Linux, Cmd+K C on macOS.

Handy for checking a snippet pulled from documentation against code you’ve already got, without creating a throwaway second file just to compare it.

Comparing an Open File Against Its Last Saved Version

Run File: Compare Active File with Saved and every unsaved edit shows up against whatever version is currently sitting on disk.

Default shortcut is Ctrl+K D on Windows and Linux, Cmd+K D on macOS.

This one’s worth running before saving over a file that’s hard to restore, a production config being the obvious example.

Every shortcut mentioned in this section, plus the rest of the editor’s keybindings, lives on one page in the VS Code workflow cheat sheet.

How to Compare Two Files Using the Terminal

Running code –diff file1 file2 from a terminal drops you straight into the diff editor, no file picker involved.

The short form, code -d, does exactly the same thing.

The code command needs to be sitting on your system PATH already for any of this to work. On macOS that means running Shell Command: Install ‘code’ command in PATH from the Command Palette first.

Anyone who hasn’t set this up yet can follow the steps for opening VS Code from the terminal before running the diff command itself.

Same command works just as well from the terminal built into the editor. Open a panel through opening a terminal in VS Code, then type the diff command directly, no need to switch windows.

This route mostly earns its keep in build scripts that need a visual diff when something fails, or CI pipelines checking generated output against an expected file. It also works fine for a quick one-off comparison if you’re already sitting in a terminal window and don’t feel like reaching for the mouse.

Nothing else here is faster for developers who basically live in a terminal.

How to Read and Navigate the Diff Editor

The diff editor marks every changed line in color, switches between a side by side view and an inline view, and gives you arrows to jump straight to the next difference.

Side by side view puts the original file on the left and the compared file on the right, with changed lines lined up across both panes. Some people call this split view out of habit. VS Code just labels it side by side.

Inline view stacks additions and deletions into a single column instead, closer to how a plain text patch file actually reads.

You can toggle between the two from the diff editor’s own menu in the top right corner, or through the Command Palette if you’d rather not touch the mouse.

Green marks the lines that got added, red marks the ones that got removed. Lines modified in place get highlighted without a solid color behind them, which trips people up the first few times until they notice the shading looks different from a straight addition.

Arrows in the toolbar step through each change one at a time, which matters more than it sounds like on a file with dozens of edits scattered through it.

The minimap on the right edge marks where changes sit across the whole length of the file too. You can spot clusters of edits before scrolling anywhere near them, which saves a fair bit of blind scrolling on longer files.

How to Compare Two Open Editor Tabs Without Selecting Files First

Right click any open editor tab and choose Compare Opened Editors, and it diffs two files that are already open without touching the Explorer pane at all.

VS Code then asks you to pick the second open tab to compare against.

This beats the Explorer method mid-session, when you’ve already got several files open and don’t want to go hunting through folders. Comparing two versions of a file pulled from different branches works well through this route too, and so does working inside a maximized editor group where the Explorer pane is hidden out of view anyway.

One catch though, both files need to already be open as editor tabs before you start. Anything not yet opened still needs the Explorer or Command Palette method.

How to Compare a File Against Its Git History

Git handles version tracking for the large majority of coding projects in active use, and industry surveys have consistently put its adoption above 90% of developers for years running. That’s most of the reason VS Code builds git-aware comparison directly into its Source Control panel instead of leaving it to an extension.

Open the Source Control panel and select any file listed under Changes.

VS Code automatically opens a comparison between your current working directory copy and the last committed version, running the same git diff logic that works from the terminal.

Files staged for commit compare against the index, while unstaged files compare against the last commit directly. Understanding staging in git makes that distinction a lot easier to read at a glance instead of guessing.

To compare against an older commit rather than just the last one, open the Timeline view in the Explorer pane and pick any prior version of the file.

GitLens extends this into full commit by commit comparison, letting you diff any two points in a file’s history instead of just the working copy against the last commit. The extension has passed 18 million installs, according to GitKraken’s own GitLens page.

How to Merge Changes Directly From the Diff View

VS Code lets you copy a change from one side of the diff editor to the other with a single click, which turns a plain comparison into something closer to a working merge tool.

Hover over any changed block and an arrow shows up next to it, pointing toward the side you’d copy the change into.

Which side stays editable depends on what you’re comparing. Two live files means both sides are editable and changes save straight to disk. Compare against Git history instead, and the historical version stays locked, read only, while only your working copy takes edits.

Microsoft added a dedicated three-way merge editor in VS Code version 1.69, released June 2022, built specifically for resolving Git merge conflicts. It shows three panels at once, Incoming, Current, and Result, according to VS Code’s own documentation.

There’s also an experimental AI-assisted conflict resolution mode tucked inside the merge editor, though it currently needs a GitHub Copilot subscription to use.

Manual copy-paste still wins over the merge arrows for conflicts spread across multiple related files. Accepting one side’s change in isolation can leave code that looks resolved on screen but doesn’t actually run.

Best Extensions for Advanced File Comparison in VSCode

The built-in diff editor covers most day to day comparisons. A few extensions fill in what it doesn’t do natively though, things like diffing text selections instead of whole files, comparing entire folders, or pulling up richer history.

Partial Diff compares any two text selections, a selection against the clipboard, or a selection against another open file, per its marketplace listing. That closes a real gap, since VS Code compares whole files by default rather than arbitrary chunks inside them.

Diff Folders stretches comparison from two files out to two entire folder trees, which is genuinely useful for spotting what got added, removed, or changed across a deployment.

GitLens adds inline blame annotations right alongside its comparison commands, so you can see who last touched a line without leaving the diff view to go check.

For extensions worth adding beyond diffing specifically, this roundup of the best VS Code extensions covers the rest of a solid setup.

When the Built-In Diff Editor Is Not Enough

An extension earns its place once you need to compare two folders instead of two files, or you’re diffing a text selection rather than a whole document. Formatting noise, whitespace changes, reordered imports, that sort of thing, burying the actual changes is the other common trigger.

Native VS Code doesn’t cover any of these on its own.

VSCode Diff Editor vs. Standalone Comparison Tools

VS Code’s diff editor is free and already open on most developers’ screens. Dedicated comparison tools trade away that convenience for things VS Code doesn’t attempt at all, like byte-level binary diffing and folder synchronization.

Scooter Software’s current pricing page lists Beyond Compare Standard at $35 for a single-user license (1 to 4 users), with the Pro edition running $70. Volume pricing brings the per-user cost down once you’re buying for a bigger team.

WinMerge ships free and open source, maintained on GitHub, though it only runs natively on Windows, which rules it out for a lot of mixed teams.

Meld is maintained by the GNOME project. Also free, also open source, and it runs across Windows, macOS, and Linux without the platform restriction WinMerge has.

Folder-level comparison is the clearest dividing line between these options. VS Code needs an extension to compare directories, while all three standalone tools build that in from the start.

Developers who only ever diff single files rarely have a reason to leave VS Code. Anyone regularly syncing whole folder trees, or comparing binary formats like spreadsheets, usually ends up reaching for one of the standalone tools instead.

Common Errors When Comparing Files in VSCode

Select for Compare Is Missing From the Right-Click Menu

This option only shows up on files, not folders. Right click a folder by mistake and the command disappears from the context menu entirely, which looks like a bug the first time it happens but isn’t one.

The Diff Editor Shows No Differences on Files That Look Clearly Different

This usually points to a line-ending mismatch rather than identical content. Git’s core.autocrlf setting controls whether line endings convert between CRLF and LF on checkout and commit, according to GitHub’s own documentation on configuring Git.

A file saved with Windows-style CRLF endings can look byte-for-byte different from the same content saved with Unix-style LF endings, even when every visible character on screen matches perfectly.

The Code Command Is Not Recognized in a Terminal

This means the command never got added to your system PATH in the first place.

1. Open the Command Palette inside VS Code
2. Run Shell Command: Install ‘code’ command in PATH
3. Restart the terminal window afterward

Git-related line-ending and configuration issues come up often enough that keeping a git cheat sheet nearby saves repeated trips back to the documentation.

Comparison Opens in a New Window Instead of the Current One

Check whether window.openFilesInNewWindow is set to “on” in your settings. That same setting affects how compare commands behave, and it’s an easy one to forget you changed months ago.

When File Comparison in VSCode Does Not Apply

The diff editor is built for text. A handful of file types and situations sit outside what it can meaningfully show, no matter how you approach it.

Binary files, images, compiled binaries, and similar formats produce no readable line by line diff. VS Code will confirm the files differ without showing you why, which isn’t much help on its own.

Very large files slow things down noticeably as size grows, since the diff algorithm has to work through every single line. GitHub’s own documentation warns developers when pushing any file over 50 MiB, and blocks pushes outright past 100 MiB, which gives a rough sense of where line by line diffing already starts turning impractical.

Entire folder structures need an extension like Diff Folders to compare. That’s not part of the native two-file comparison workflow.

Three-way merges during conflict resolution run through the separate merge editor instead of the standard diff view. Related problem, different interface.

Reaching for the right tool from the start saves time. Forcing the standard diff editor onto a binary file or a 500 MB log dump usually costs more time than it saves.

FAQ on How To Compare Two Files In Vscode

Can VS Code ignore whitespace when comparing files?

Yes, and it’s on by default. The diffEditor.ignoreTrimWhitespace setting skips leading and trailing whitespace changes in the diff view automatically.

It only trims whitespace though, so swapping tabs for spaces inside a line can still show up as a change even with the setting on.

Does the diff editor highlight changes within a single line, not just whole lines?

It does. Beyond marking whole lines green or red, the diff editor highlights the exact characters that changed inside a modified line with a deeper shade, and Microsoft’s own VS Code repository documents this character-level behavior directly.

Can I compare two files open in separate VS Code windows?

Not directly, no. The diff editor only compares files open within the same window.

Move one file into the other window first, or open both inside a single workspace, then run any standard compare command from there.

Is there a keyboard shortcut to jump straight into a diff comparison?

No default shortcut opens the diff picker directly. You’d need to assign one manually to File: Compare Active File With… through keyboard shortcut settings.

Inside an open diff though, Alt+F5 and Shift+Alt+F5 already jump between individual changes without any setup.

Does VS Code support comparing image files visually?

To some degree. VS Code shows a visual preview for changed image files tracked by Git, so you can see before and after side by side.

It’s not pixel-level comparison the way dedicated image diff tools handle it, so don’t expect much beyond a quick visual check.

Can I set VS Code as Git’s default diff tool for terminal commands?

Yes. Run git config –global diff.tool vscode, then set difftool.vscode.cmd to code –wait –diff $LOCAL $REMOTE.

Typing git difftool afterward opens every changed file straight into the VS Code diff editor, one after another.

Does file comparison work over a Remote-SSH or WSL connection?

It does. The diff editor reads file content regardless of where it actually lives, so comparisons behave the same inside Remote-SSH, WSL, or Dev Containers sessions.

No extra setup needed beyond the remote connection already being active.

Can VS Code compare more than two files at the same time?

No. The diff editor is built around exactly two panes, original and compared, and that’s a hard limit rather than a setting you can change.

Comparing three or more versions at once needs a dedicated tool like Beyond Compare, or the separate merge editor for Git conflicts specifically.

How do you close a diff view without closing the underlying files?

Close the diff editor tab itself, same as closing any other tab, using the x icon or Ctrl+W.

The two files stay open in their own tabs if you had them open separately to begin with.

Can I compare two Git branches instead of two individual files?

Yes, through the terminal. git diff branch1 branch2 — filename compares that file’s content across two branches directly, no need to check either one out first.

The same underlying approach applies when you compare branches on GitHub itself, just through a different interface.

Picking a Default and Sticking With It

Most developers only need one of these methods on any given day. Learning how to compare two files in VS Code pays off fastest once you settle on the Explorer right-click method as your default and reach for the Command Palette only when a file sits outside your open folder.

Save the terminal route for automation scripts rather than daily habit. That single swap probably saves more time than memorizing every keyboard shortcut in the toolkit combined.

Install an extension only once the built-in diff editor hits a real wall: folder trees, binary formats, or a selection instead of a whole file.

One more thing worth expecting going in. A clean comparison depends on matching line endings, not just matching content, and that catches more people off guard than it should.

• Author
• Recent Posts

Bogdan Sandu

Bogdan Sandu is a front-end developer at TMS Outsource with 8+ years of experience in web technologies. He writes about developer tools, software platforms, and web workflows based on daily hands-on use.

Latest posts by Bogdan Sandu (see all)

• What Are the Best Kajabi Alternatives for Growing Your Online Business? - August 19, 2026
• Google Play Internal Testing: How to Set It Up - August 18, 2026
• 7 Top-Rated SASE Solutions for Hybrid Enterprises - August 18, 2026