How to Verify Your Gnuplot Installation (Checklist)

A gnuplot install is verified in under a minute: open a new terminal, run gnuplot --version, and draw one test plot. For the current release the version command prints exactly gnuplot 6.0 patchlevel 5. Work through this checklist in order.

The Checklist

1. Open a fresh terminal. Terminals opened before the installation do not see PATH changes — this alone explains most “not found” reports.
2. Check the version:

   gnuplot --version

   Expected output for the current release:

   gnuplot 6.0 patchlevel 5

   An older patchlevel simply means your package source (distribution repository, winget, Homebrew) has not caught up with 6.0.5 yet — the install itself is still valid.

3. Check which binary runs:

   which gnuplot

   On Windows PowerShell use where.exe gnuplot. If you installed more than once (package plus source build), this shows which copy wins.

4. Draw a test plot:

   gnuplot
   plot sin(x)
   exit

   A window with a sine curve proves the graphical terminal works.

5. Test file output:

   gnuplot -e "set terminal pngcairo; set output 'test.png'; plot sin(x)"

   A test.png file should appear in the current folder — this is the mode most scripts and pipelines actually use.

PATH Not Working? Symptoms and Quick Fixes

• “gnuplot is not recognized / command not found” in a fresh terminal: the install did not register on PATH. On Windows, re-run the installer and tick “Add application directory to your PATH”. On macOS with Homebrew, run the brew shellenv line Homebrew suggested. On Linux package installs this should never happen — check for a typo before anything else.
• Version prints an old release: an older gnuplot earlier on your PATH is shadowing the new one. Step 3 shows the path that is actually running; adjust PATH order or remove the old copy.
• Version works but no plot window: the binary is fine; the graphical terminal is missing or unreachable (common on headless servers). Use the pngcairo test in step 5 to confirm file output works.

This checklist separates a broken install from a PATH hiccup in most cases. If gnuplot still misbehaves after every box is ticked, re-install cleanly from the packages on the download page and re-run this page top to bottom.