Plugins & Extensions

Advanced Compositing & Retouching

Chapter 9 · Plugins & Extensions

Chapter 5 mentioned that GIMP's Wavelet Decompose script isn't part of a default install and would need installing separately — a promise this chapter now delivers on. More broadly, both Photoshop and GIMP can be extended well beyond their own built-in feature set with plugins and extensions written by someone other than the core development team. How that ecosystem is structured, and what it costs, is a real, practical difference between the two tools — not a minor footnote.

What a Plugin or Extension Actually Is

A plugin (Photoshop's usual term) or extension/script (GIMP's usual terms) is code, written by a third party, that adds new capability to the base application — a new filter, a new panel, a new automated workflow — installed separately from the application itself rather than being part of what ships out of the box.

Photoshop's Plugin Ecosystem

Photoshop's plugin ecosystem is built around Adobe Exchange, a marketplace of third-party plugins and panels built by independent commercial developers on top of Photoshop's own plugin API. Entire categories of professional retouching and workflow tools exist as commercial plugin suites — specialized noise-reduction engines, panel-based batch tools, texture and sky-replacement libraries — most sold as a one-time purchase or ongoing subscription, separate from the Creative Cloud subscription itself. This is a genuine, real cost on top of Photoshop's own subscription, not a hypothetical one.

Installing a GIMP Script: Wavelet Decompose, Concretely

GIMP's installation model for a Script-Fu script is structurally simple, and worth walking through concretely since Chapter 5 left it as a forward reference:

  1. Download the script file (typically a plain text file with a .scm extension, like Wavelet Decompose).
  2. Find GIMP's own scripts folder via Edit > Preferences > Folders > Scripts — GIMP lists the exact directory path it scans for scripts.
  3. Copy the .scm file into that folder.
  4. Run Filters > Script-Fu > Refresh Scripts to make GIMP pick up the new script immediately — no restart required.

A Python-Fu plugin follows a similar idea but installs into a separate plug-ins folder instead of the scripts folder, and on Linux/macOS may additionally need executable permissions set on the file before GIMP will recognize it. Either way, this is a fundamentally different installation model than Photoshop's typical plugin installer — a script is just a text file dropped into the right folder, not a packaged, signed installer application.

GIMP's Free, Community-Maintained Ecosystem

The overwhelming majority of GIMP scripts and plugins — including Wavelet Decompose — are free, written and shared by individual community members through forums, GitHub repositories, and community script collections, reflecting the same free/open-source ethos as GIMP itself. There's no central paid marketplace curating, vetting, or guaranteeing ongoing support for these scripts the way Adobe Exchange does for its commercial listings.

AspectPhotoshopGIMP
MarketplaceAdobe Exchange — curated, commercialNo central marketplace — forums, GitHub, community collections
Typical costOften paid — one-time purchase or subscriptionOverwhelmingly free
InstallationPackaged installer applicationCopy a script file into a designated folder, then refresh
Ongoing support/compatibilityVendor-maintained, often part of what the price coversCommunity-maintained, no guarantee of upkeep
Check compatibility before installing any script or plugin
Always confirm a script or plugin is documented as compatible with your specific application version before installing it. This matters especially for GIMP: when GIMP 2.10 introduced the GEGL engine (Chapter 4), a number of older community Script-Fu scripts, written against the prior engine's internals, stopped working correctly without updates. A script's own documentation or the community page it was shared on is usually the fastest way to confirm it's still actively compatible before relying on it for real work.
"Free" and "paid" carry a real, honest tradeoff — not a simple win for either side
A commercial Photoshop plugin's price is often genuinely paying for something real: vendor-maintained compatibility as Photoshop itself updates, and a support channel if something breaks. A free GIMP script has no equivalent guarantee — if it stops working correctly after a GIMP update (exactly as happened broadly with the GEGL transition), there's no vendor obligated to fix it, only whichever community member originally wrote it, if they're still maintaining it at all. Free is a genuine, real advantage — but it isn't a strictly better deal in every respect; it trades guaranteed vendor support for no cost, rather than offering both at once.

Hands-On Exercises

Exercise 1

Walk through, step by step, how you would install the Wavelet Decompose script into GIMP so it appears as a usable filter.

📄 View solution
Exercise 2

A colleague says "GIMP's plugin ecosystem is strictly better than Photoshop's, since everything is free." Using this chapter's own warning box, explain what this claim overlooks.

📄 View solution
Exercise 3

A studio updates GIMP to a new major version, and a community script they've relied on for years suddenly stops working correctly. Using this chapter's own material, explain why this happened and what could have reduced the risk beforehand.

📄 View solution

Chapter 9 Quick Reference

  • Photoshop: Adobe Exchange marketplace, largely commercial plugins with vendor-maintained support
  • GIMP: no central marketplace — scripts shared via forums/GitHub, overwhelmingly free, community-maintained
  • Installing a GIMP Script-Fu script: copy the .scm file into the Scripts folder (Edit > Preferences > Folders > Scripts), then Filters > Script-Fu > Refresh Scripts
  • Python-Fu plugins install into a separate plug-ins folder, and may need executable permissions on Linux/macOS
  • Always check a script/plugin's compatibility before installing — GIMP's GEGL transition broke a real number of older scripts
  • "Free" and "paid" trade off cost against guaranteed vendor support — neither is a strictly better deal in every respect