PluginDate.com

Beta PluginDate is in test operation. Results are being improved step by step – if something appears to be wrong, please tell us (form at the bottom of the page).

Which of your plugins have a newer version?

For macOS and Windows. No installation, no sign-up. A short script lists your installed plugins into a CSV file; drop it here and see what to update in seconds.

1 Run the scan script

Choose your computer:

  1. 1 Copy the script
  2. 2 Paste in TerminalPaste in PowerShell
  3. 3 Wait for “Done”
  4. 4 Drop it below
Not sure about running a script from the internet? Check it yourself

The script is short and readable – you can see every line below. If you want a second opinion, ask any AI chat, for example ChatGPT (works without an account), Claude or Gemini:

  1. Click the button below – it copies the question together with the whole script.
  2. Open an AI chat, e.g. chatgpt.com, claude.ai or gemini.google.com, paste it and send.

Can I run this script on my computer? Is it safe? What exactly does it do?


      
    
What exactly does the script do?
  • For each plug-in it reads its small description files (macOS: Info.plist; Windows: moduleinfo.json, Info.plist, version info) and the header of its program file – only to get the name, vendor, version, format, CPU type and plug-in ID. Plug-ins are never started.
  • It downloads nothing, installs nothing and sends nothing. The result is just a file on your Desktop – open and edit it as you like.

2 Drop the CSV here

The file is first checked in your browser only. It is sent when you confirm, and only these fields: vendor, plugin name, version, build, format, architecture and plugin ID, plus your system version (e.g. macOS 15.7 or Windows 11). We store them anonymously and de-duplicated – they keep the database current for everyone. We do not store the file, your IP address or anything that could identify you or your studio.

Studio comparison – several computers at once

For studios with several rooms, broadcasters and anyone who keeps more computers in sync. Run the script on every computer, rename the files so you can tell them apart (e.g. plugins_list_Studio_A.csv, plugins_list_Studio_B.csv) and drop all of them here at once (up to 10).

You get one table: one row per plug-in, one column per computer, plus the newest version. Filters show only differences, plug-ins missing somewhere or outdated somewhere; the table can be exported to CSV.

Pro Tools session check – will this session open here?

For engineers who receive or move sessions between studios. In Pro Tools open the session and choose File → Export → Session Info as Text (keep “Include Plug-In List” ticked). Drop that text file together with the plug-in list of the computer that should open the session.

For every plug-in used in the session you see whether it is installed, whether the installed version is older, or whether it is missing or has no AAX version. Only the plug-in list from the session is sent – track names, clips and file paths stay on your computer.