Free online LNK to PDF converter

A PDF may be required when a help-desk system, audit record, or document repository rejects Windows shortcut files. The useful output is either a PDF made from the shortcut’s target document or a static PDF report showing the shortcut’s settings.

What LNK files contain

LNK is the Windows Shell Link format used by Windows Explorer, installers, Start menu entries, and desktop shortcuts. A .lnk file can store a target path, command-line arguments, working directory, icon location, description, hotkey, and tracking information.

A shortcut does not contain the target document, program, or folder contents. Double-clicking it asks Windows to locate and open the target, which may be a local file, network location, removable drive, or application executable.

Do not open an unknown shortcut by double-clicking it. A malicious LNK can launch commands or programs. Inspect its properties first, and scan untrusted files with endpoint security software.

What PDF provides

PDF is a fixed-layout document format supported by document-management systems, browsers, desktop viewers, and mobile devices. It preserves a readable document or metadata report for sharing and archiving, but it cannot retain Windows shortcut behavior, icon associations, or automatic target resolution.

Create a PDF from the target file

1. Right-click the shortcut and select Properties. On the Shortcut tab, inspect Target, Start in, and Arguments.
2. If Target identifies a document, open the target itself rather than the shortcut. A target ending in .pdf is already a PDF and can simply be copied.
3. Use the application that owns the target file to export it. In Microsoft Word, Excel, and PowerPoint, use File → Export → Create PDF/XPS or File → Save As and select PDF. For applications without PDF export, use File → Print → Microsoft Print to PDF.

Native PDF export is preferable to printing because it usually preserves selectable text, hyperlinks, bookmarks, and document structure better than a virtual printer. If the source document is non-confidential and no desktop application is available, Adobe Acrobat’s online conversion tools can convert supported Word, Excel, PowerPoint, and image files; upload the resolved source file, not the .lnk file.

If the target is an executable such as app.exe, a folder, or a command with arguments, it has no document content to convert. Produce a shortcut-properties report or separate technical documentation instead.

Create a PDF report of shortcut properties

Windows can read shortcut metadata locally even if the target has been deleted. Open PowerShell and run the following commands, replacing the sample path:

$link = 'C:\Users\Name\Desktop\Example.lnk'
$shell = New-Object -ComObject WScript.Shell
$s = $shell.CreateShortcut($link)

[pscustomobject]@{
  'Shortcut file'     = $link
  'Target path'       = $s.TargetPath
  'Arguments'         = $s.Arguments
  'Working directory' = $s.WorkingDirectory
  'Description'       = $s.Description
  'Icon location'     = $s.IconLocation
  'Hotkey'            = $s.Hotkey
} | Format-List | Out-File -LiteralPath "$PWD\lnk-report.txt" -Encoding utf8 -Width 4096

Open lnk-report.txt in Notepad, select File → Print, choose Microsoft Print to PDF, and save the result. This creates a static record of the values Windows can read from the shortcut without executing its target.

Compatibility and quality limits

A shortcut may reference a path such as \\server\share\file.docx, a mapped drive, or a removable device that is unavailable on another computer. The report records the stored value; it does not prove that the target still exists, is accessible, or will open successfully.

If the target was deleted, moved, or is on an unavailable network share, no converter can reconstruct its missing contents from the LNK file. Recover the original from a backup, cloud-sync version history, email attachment, source repository, or file-recovery process.

Avoid uploading LNK files to generic conversion websites. Such services cannot access targets on your PC and may expose usernames, internal server names, paths, URLs, and command-line arguments. A local PowerShell report and Microsoft Print to PDF are the appropriate method for shortcut metadata.