greenshot

What this screenshot job needs

People who type this tool usually want a free desktop screenshot tool they can install once and keep between tickets. The job is capturing a region or window, annotating quickly, and exporting to clipboard or file on a PC you control, not a browser demo and not a paid graphics seat.

The upstream open-source project behind that search ships a Windows desktop client. Shutter Quill maps the doors: the Windows RELEASE.exe on GitHub Releases tags, and the verified winget id Greenshot.Greenshot. There is no Homebrew cask for this guide.

Related: releases, GitHub, download safely, Windows install.

Why this desktop path

A dedicated this tool install stays on the machine after Setup. You control the update door. Hotkeys, destinations, and editor preferences live in the client instead of a temporary browser tab that forgets your capture settings.

Winget keeps fleet images honest when the catalog is allowed. RELEASE.exe keeps labs honest when package managers are blocked. Official macOS and Linux binaries are not published on the non-prerelease tags this guide covers, so Windows remains the supported stranger-safe path for this screenshot tool.

Other screenshot tools still win when a team already standardised on ShareX automation or the built-in Snipping Tool. Browser download pages do not replace a tray client with clear hotkeys. Choose this tool when you want GPL-3.0 source, a named Releases asset, and a lightweight editor without inventing a brew cask.

Install by operating system

Windows is the primary stranger-safe path with the Windows RELEASE.exe. macOS and Linux have no official release binaries on the stable tags verified here, and there is no Homebrew cask for this screenshot tool.

Run the Windows winget line when App Installer is present:

winget install -e --id Greenshot.Greenshot

When package managers are blocked, take the Windows RELEASE.exe from the current non-prerelease tag on GitHub Releases. Longer Windows pages: install on Windows. Winget-only walkthrough: winget install. Installer walkthrough: Windows installer.

Compare common doors

Use this table when a teammate asks which path matches your imaging rules. Every cell stays honest about Windows-primary support for this screenshot tool and brew NONE.

Eight steps after Setup

These steps match the HowTo schema above. Stay on Windows for the prove path with this tool.

1. Open the official release door. Open GitHub Releases for the upstream repository on a current non-prerelease tag and confirm you see Greenshot-INSTALLER-*-RELEASE.exe, not an UNSTABLE or UNSIGNED build.
2. Prefer the RELEASE installer. Take the Greenshot-INSTALLER-*-RELEASE.exe asset from the live non-prerelease tag. Write the filename on the machine ticket. Skip UNSTABLE and prerelease tags.
3. Or run the verified winget id. When App Installer is present, run the verified winget command. That id is YAML-verified in microsoft/winget-pkgs.
4. Finish the installer. Approve UAC when Windows prompts. Complete the Inno Setup wizard so the Start Menu and tray shortcut land where you expect.
5. Confirm the tray icon. Launch this tool and confirm the tray icon appears before you change hotkeys or default destinations.
6. Set one capture hotkey. Open Preferences from the tray and set a PrintScreen-family or custom hotkey you can remember on this desk.
7. Prove one region capture. Capture a small region, open the editor or clipboard path you chose, and save one PNG. That proves the install before you trust it for tickets.
8. Keep one update door. Return to the same GitHub Releases RELEASE.exe or the verified winget upgrade. There is no Homebrew cask. Skip adware wrappers that only rank for screenshot searches.

After install checklist: installed. First-run detail: first run.

First hour after install

Spend the first hour proving capture, not collecting every plugin. Set one hotkey, choose clipboard or file output, capture one region, and save one PNG with this tool. Write the install door on the machine card so next month’s update does not invent a new mirror.

Optional destinations such as printers or upload targets stay under your control. You can keep this tool fully local with clipboard and folder saves. Preferences let you tune the editor after capture without rebuilding hotkeys each week.

Related: for this computer, hotkeys, is it safe.

Switching and comparing

People leaving ShareX, Windows Snipping Tool, or Flameshot usually keep the same screenshot folders on disk. this tool does not silently import rival hotkey maps, so plan a quiet half hour to rebuild destinations.

Compare feature posture without invented scores: vs Snipping Tool. Migration walkthroughs: greenshot: switch from ShareX, greenshot: switch from Snipping Tool, greenshot: switch from Flameshot.

Mistakes that waste an evening

• Installing a Softonic-style wrapper that only ranked for this screenshot tool searches
• Shipping an UNSTABLE UNSIGNED build into a shared lab image
• Assuming a Homebrew cask exists for Mac desks
• Changing every destination before proving one region capture
• Leaving ShareX and this tool fighting over the same PrintScreen hotkey

Search ads often promote mirrored setups that bundle extra offers around this tool. Prefer GitHub Releases or the verified winget id. Write the filename you installed beside the machine name.

Travel laptops benefit from a single documented installer door written beside the screenshot folder. Lab images drift when someone installs a second mirror during a blocked SmartScreen prompt. Prefer returning to the same Releases URL or winget id instead of inventing a new download mid-flight.

Install and setup guides

Child guides answer one install or migration question each for this screenshot tool. Every guide links back to this pillar.

Cluster pages: releases, GitHub, download safely, how to install winget.

Capture habits that age well

Keep one default destination per desk when you juggle clipboard and file saves. Write the screenshot folder on the machine card so a substitute does not invent a second Downloads path during a SmartScreen scare.

Shared apartments should document which Windows user owns the tray session. Two people sharing one profile will collide on hotkeys and destinations. Separate OS accounts keep capture maps honest.

• Pin the RELEASE.exe filename beside the OS build
• Prove one region capture after every reimage
• Uninstall adware wrappers before you blame hotkeys

Imaging season without drama

Classroom and helpdesk images should freeze only after a reboot test with this tool open in the tray. Prefer the newest non-prerelease tag that publishes the Windows RELEASE.exe. Keep brew NONE written on the card so Mac volunteers are not sent hunting.

Writing clearer tickets

Vague capture-does-not-work notes waste mornings. Ask for the tag name, the RELEASE.exe filename, and a screenshot of Preferences after install. Substitutes can then recreate the desk without guesswork when this tool is the documented tool.

When you retire a machine, uninstall this tool and clear screenshot folders that still hold private work according to retention rules.

How do I install greenshot on Windows?

Prefer the Windows RELEASE.exe from the current non-prerelease tag on the upstream repository GitHub Releases, or run the verified winget id the verified winget package id when App Installer is present. Both doors map to the same GPL-3.0 Windows screenshot tool. Avoid renamed setups from advertising download portals.

Where should I download the installer?

Use GitHub Releases for the upstream repository or the verified winget package. Those doors publish named RELEASE.exe assets on stable tags. Softonic-style portals often wrap the same search intent with extra installers you did not ask for.

Is it free and open source?

Yes. this tool is free under the GPL-3.0 licence on the upstream repository. You can install, capture, annotate, and export without buying a seat. Optional destinations and plugins stay under your control on the Windows PC you manage.

Can I switch from ShareX or Snipping Tool?

Yes. Install from GitHub Releases or winget, then rebuild hotkeys and destinations by hand. ShareX workflows and Windows Snipping Tool history do not import automatically. Guides cover switch-from paths for ShareX, Snipping Tool, and Flameshot.

Does it work offline?

After the first download, this tool captures, annotates, and saves locally without a network. You only need connectivity when you choose an upload destination or check GitHub Releases for a newer RELEASE.exe.

Is there a Mac or Linux build?

No official macOS or Linux release binary is attached to the non-prerelease tags this guide verifies. Homebrew has no this tool cask. Prefer the Windows RELEASE.exe path and keep brew NONE honesty on lab cards.

• Quote the winget id and Releases URL in every runbook
• Pin RELEASE.exe filenames beside the OS build
• Keep brew NONE on printed lab cards for this screenshot tool

Internal runbooks should quote the winget id Greenshot.Greenshot and the Releases URL without marketing adjectives. Staff skim under stress. A short checklist with five boxes outperforms a three-page essay that nobody finishes.

• Include the tag name and RELEASE.exe filename on every escalation
• Paste the winget command verbatim for package-manager installs
• Keep brew NONE on the printed card beside the Releases URL

When a machine retires, uninstall this tool and clear screenshot folders that still hold private work according to your retention rules. Prefer the newest non-prerelease tag that publishes RELEASE.exe. UNSTABLE lines stay out of golden images.

Lab leads who image every semester should rehearse the prove-capture step before freeze day. A quiet checklist with the Releases URL, the winget id, and brew NONE beats a long essay nobody finishes under stress when this tool is the desk standard.

Writers who only wanted a quick region capture still benefit from the same stranger-safe doors. Start small, capture once, then tune destinations. That rhythm is how shared clubs avoid weekend outages when someone pastes a random mirror into the group chat for this screenshot tool.