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:
- Download the script file (typically a plain text file with a
.scmextension, like Wavelet Decompose). - Find GIMP's own scripts folder via Edit > Preferences > Folders > Scripts — GIMP lists the exact directory path it scans for scripts.
- Copy the
.scmfile into that folder. - 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.
| Aspect | Photoshop | GIMP |
|---|---|---|
| Marketplace | Adobe Exchange — curated, commercial | No central marketplace — forums, GitHub, community collections |
| Typical cost | Often paid — one-time purchase or subscription | Overwhelmingly free |
| Installation | Packaged installer application | Copy a script file into a designated folder, then refresh |
| Ongoing support/compatibility | Vendor-maintained, often part of what the price covers | Community-maintained, no guarantee of upkeep |
Hands-On Exercises
Walk through, step by step, how you would install the Wavelet Decompose script into GIMP so it appears as a usable filter.
📄 View solutionA 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 solutionA 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 solutionChapter 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
.scmfile 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