UTILITY / PROJECT FORENSICS

See what your DAW project depends on.

Drop a saved project or session. PluginChek scans it locally, identifies plugin references, explains what they do, shows the evidence it found, and can compare the project against your installed plugin files.

PROJECT → CONTAINER → STRINGS → PLUGINS → REPORTNO UPLOAD / NO ACCOUNT / NO SERVER

01 / PROJECT INPUT

Analyze project files

⌁

Drop project files here.als .rpp .flp .song .bwproject .cpr .npr .ptx .logicx .band .reason .zip + unknown binaries

Local by design. Files are read with browser APIs and are not uploaded by PluginChek.

02 / OPTIONAL CROSS-CHECK

Installed plugin inventory

Select your VST/AU/AAX/CLAP plugin folder, or provide an exported text/CSV/JSON file list. PluginChek compares project references against filenames and paths.

Select plugin folderLoad inventory file

No inventory loaded

Advanced scan options

Min string length Deep archive scan Show low-confidence evidence Keep raw evidence

HOW IT WORKS

Exact where possible. Evidence-driven everywhere else.

Some DAWs store readable XML or text. Others use proprietary binary formats. PluginChek uses format-aware decoding for known containers, then falls back to printable-string and plugin-signature analysis. Each finding shows confidence and evidence so you can see what was recovered rather than trust a black box.

See what your DAW project depends on.

Analyze project files

Installed plugin inventory

Project dependency report

Recovered plugins

What was scanned

Take the report with you

Exact where possible. Evidence-driven everywhere else.