What Is a .lnk File? Windows Shortcuts Explained

If you've ever right-clicked a file on your Windows desktop and chosen "Create shortcut," you've already created a .lnk file — even if you never saw that extension. These small but important files are a core part of how Windows organizes and navigates the file system, yet most users never think about them until something goes wrong.

The Basic Definition: A Pointer, Not a File

A .lnk file (pronounced "link file") is a Windows Shell Link — a shortcut file that points to another object on your system. That object could be:

• An executable program (like chrome.exe)
• A folder or directory
• A document, image, or media file
• A network location or shared drive
• A specific URL or web resource (when paired with a browser)

The .lnk file itself contains no actual content from the target. It's a small binary file — typically just a few kilobytes — that stores metadata telling Windows where to find the real file and how to open it.

When you double-click a shortcut on your desktop, Windows reads the .lnk file, follows the stored path, and launches the target. You never interact with the .lnk directly — it's invisible infrastructure.

What's Actually Inside a .lnk File

Under the hood, a .lnk file follows the [MS-SHLLINK] binary file format, a Microsoft specification. It can store a surprisingly detailed package of information:

That last two items matter more than most people realize — they're part of why shortcuts can sometimes still work even when a file moves slightly, but break completely when a drive is reformatted.

Why Windows Hides the .lnk Extension

By default, Windows hides the .lnk extension from File Explorer — even when "show file extensions" is turned on. This is intentional behavior: shortcuts are meant to feel like transparent access points, not separate files.

You'll notice this means a shortcut to notepad.exe just shows as "Notepad" on your desktop, not "Notepad.lnk." The system icon (the small arrow overlay in the corner) is the only visual indicator that it's a shortcut rather than the actual file. 🔍

Where .lnk Files Live on Your System

.lnk files are scattered throughout Windows in several key locations:

• Desktop — both the user desktop (C:Users[Name]Desktop) and the public desktop (C:UsersPublicDesktop)
• Start Menu — program shortcuts that populate the Start menu are almost all .lnk files stored in AppDataRoamingMicrosoftWindowsStart Menu
• Taskbar pinned items — stored in a similar AppData subfolder
• Recent files list — Windows automatically generates .lnk files in AppDataRoamingMicrosoftWindowsRecent every time you open a file, creating a navigation history

That last point has privacy implications. The Recent folder is a persistent log of file access, and forensic analysts frequently examine .lnk files in that folder to reconstruct user activity — even after the original files have been deleted.

.lnk Files and Security Risks ⚠️

.lnk files have a documented history as an attack vector. Because Windows executes the target when a shortcut is opened, malicious .lnk files have been used to:

• Launch hidden scripts or executables from unexpected locations
• Exploit vulnerabilities in how Windows renders shortcut icons (the Stuxnet worm famously used this technique in 2010)
• Deliver malware disguised as innocent-looking desktop shortcuts

Modern Windows versions have patched most of the known icon-parsing vulnerabilities, but the underlying risk remains: a .lnk file from an untrusted source can execute something you didn't intend to run. This is why security-conscious users treat unexpected .lnk files — especially those arriving via email attachments or downloads — the same way they'd treat any unknown executable.

When .lnk Files Break

A shortcut stops working when the target path it stores no longer exists. Common causes:

• The program was uninstalled
• A file was moved or renamed
• An external drive was disconnected or assigned a different drive letter
• A network share became unavailable

Windows will display an error like "The item that this shortcut refers to has been changed or moved." The .lnk file itself still exists — it just can't resolve its stored path anymore. You can right-click the shortcut and use Properties → Change Target to repoint it without recreating it from scratch.

.lnk vs. Other Shortcut Types

Windows isn't the only environment using shortcut-style files, and .lnk files are specific to Windows Shell:

Symbolic links (symlinks) are often confused with .lnk files, but they're fundamentally different — symlinks are handled at the file system level by the OS kernel, while .lnk files are a Windows Shell feature interpreted at the application layer.

The Variables That Change How .lnk Files Behave

How .lnk files affect your experience depends heavily on context:

• Your Windows version determines which .lnk vulnerabilities have been patched and how the shell resolves broken shortcuts
• How you use your file system — heavy use of external drives, network shares, or cloud-synced folders increases the chance of broken shortcuts
• Your security posture — whether you're running in a managed enterprise environment versus a personal machine affects how much scrutiny unusual .lnk files deserve
• Whether you're a developer or power user — those using command-line arguments stored in shortcuts, or automating tasks via Start Menu entries, interact with .lnk metadata in ways casual users never encounter

For most people, .lnk files are background infrastructure. For others — IT administrators, security researchers, digital forensics professionals, or anyone troubleshooting a stubborn broken shortcut — understanding what's inside them is genuinely useful. Where .lnk files sit on that spectrum for you depends entirely on how you use Windows and what problem, if any, brought you here.