How this works: this page reads the Compound File Binary (OLE2) container format and the embedded Shell Link (.lnk) entries directly in your browser tab, with plain JavaScript. No WebAssembly, no CDN dependency, nothing uploaded — your file is never sent anywhere.
Accuracy note: the container format and the shortcut format are both public specifications, and are parsed strictly. The "DestList" metadata (pin order, access count, recorded path) uses a format Microsoft has never published, reverse-engineered by the forensics community — it's offered as best-effort supplementary detail; if it can't be parsed cleanly, the shortcuts are still shown from their own data.
Reading a Jump List on Mac or Linux
Jump list files live under Windows' %AppData%\Microsoft\Windows\Recent\AutomaticDestinations folder, but the container format underneath (OLE2 Compound File Binary, plus embedded Shell Link entries) is a documented, platform-independent binary layout. Copy the file to any computer and drop it in above — no Windows tooling required.
Troubleshooting
DestList metadata (pin order, access count) didn't parse for one or more entries
Unlike the container and shortcut formats, the "DestList" stream's internal layout was never published by Microsoft — it's reverse-engineered by the digital-forensics community and offered here as best-effort supplementary detail. When it can't be read cleanly, the shortcuts themselves are still shown correctly from their own well-specified data.
I don't see the file or app I expected in the list
Each Jump List file belongs to exactly one application, named by an AppID hash in its filename (not the app's actual name). Check %AppData%\Microsoft\Windows\Recent\AutomaticDestinations\ for the right file — Windows keeps a completely separate file per app.
Prefer the command line?
Eric Zimmerman's JLECmd is a well-known digital-forensics command-line tool for jump lists, built on .NET so it also runs on Mac and Linux via the .NET runtime: