ShareX: a Windows capture app whose real product is the after-capture task chain

v21.0.0 shipped in July, and the branch has moved since

ShareX is a free and open source screenshot tool, screen recorder, file sharing tool and productivity application for Windows, released under the GPL-3.0 with the licence file named LICENSE.txt and a Licenses directory beside it. The recent tags are v20.1.0 on 2026-05-06, v20.2.0 on 2026-05-22 and v21.0.0 on 2026-07-03. The default branch is develop, and the last push to it was on 2026-09-29.

So the newest stable build is roughly three months behind the branch, which is normal for a project with a development line and a stable line, and the README makes the choice explicit: you can install the regular setup version, use a portable version, or try development builds if you want the newest changes before a stable release. The useful part is the phrasing. A development build is what the develop branch produces, and it is a different risk from the tag, so a team that pins should pin the tag and read the changelog at getsharex.com/changelog rather than assuming the newest download is the newest release.

The capture list ends where the task chain begins

The capture methods are ordinary and complete: fullscreen, active window, active monitor, region, scrolling screenshot, last region, custom region, screen recording, GIF screen recording and auto capture. That list is the least interesting part of the product.

The mechanism is what runs afterwards. A captured image or recording can be copied to the clipboard, saved to a file, opened in the image editor, uploaded, printed, shown in Windows Explorer, passed to a custom action, scanned for a QR code, or run through OCR to recognise text. The same idea applies after the upload, where ShareX can copy the URL to the clipboard, open it, shorten it, show a QR code or run other configured tasks. The README spells out the chain it enables: capture a region, annotate the image, save it locally, upload it to a destination, shorten the URL, and copy the final link to the clipboard. That sequence is the product, and it is why the tool is popular with people who file bug reports rather than people who take a picture.

Twenty-five utilities in one window, and the cost of that surface

The productivity list runs to twenty-five entries and reaches well past screenshots: a color picker, a screen color picker, a ruler, pin to screen, an image editor, an image beautifier, image effects, an image viewer, a background remover, an image comparer, an image combiner, an image splitter, an image thumbnailer, a video converter, a video thumbnailer, analyze image, OCR, a QR code tool, a hash checker, a metadata viewer, a directory indexer, a clipboard viewer, a borderless window, inspect window and a monitor test.

That is a lot of surface to configure, and the README does not pretend otherwise. It says the workflow system is one of the main reasons ShareX is popular with power users, and that simple tasks can stay simple while advanced users automate detailed processes. The honest reading is that you get two products in one: a screenshot app that works the moment you press the hotkey, and a task runner whose value is proportional to how much of that list you wire up. A new install starts as the first and becomes the second only if you spend the afternoon on hotkeys, after-capture tasks and upload destinations.

The image editor is part of the same loop rather than a separate app: crop, annotate, redact, highlight, shapes, arrows, text, freehand drawing, image insertion, cursor insertion, blur, pixelate, magnify, spotlight, cut out, background editing and image effects, all reachable before you copy, save or upload. Blur, pixelate and a smart eraser are the tools to reach for first when the screenshot contains something private, and they are listed as such.

Custom uploaders, with guides for S3, GCS and R2

ShareX uploads images, text, files, folders, clipboard content and URLs to many destinations, and the built-in list is not the limit. Advanced users can create custom uploaders for services that are not built in, and the project publishes guides for Amazon S3, Google Cloud Storage and Cloudflare R2.

That is the part that makes ShareX usable in a team rather than only on a personal machine. The built-in destinations are convenience, and convenience means your screenshot goes to a third-party host; the documented alternative is your own object storage, with a custom uploader pointed at a bucket you control. The README frames both cases, personal screenshot sharing and team workflows where files need to go to controlled storage, and that second case is the one to read twice if your screenshots ever contain internal URLs or ticket text.

Whichever route you take, the after-upload tasks are the same, so the chain in the previous section works identically against your own bucket: upload, shorten, copy.

Screen recording is in the list, audio is nowhere in it

Screen recording and GIF screen recording are both listed among the capture methods, and the rest of the capture list is visual: fullscreen, active window, active monitor, region, scrolling screenshot, last region, custom region and auto capture.

Nothing anywhere in the repository describes recording audio alongside the picture. There is no mention of a microphone, a system audio device, an audio track or an audio setting. That is worth stating plainly, because recording a narrated walkthrough is a common reason to reach for a screen recorder, and ShareX as documented does not claim to do it. The README also does not give the hotkey for any capture method, the scrolling capture settings, or the dialog that configures recording, so a reader arriving with a specific recording question has to find the answer in the application rather than the documentation.

For pure visual capture, the scrolling screenshot and the last region entries are the two that save the most time on a repeated task, and both are named in the list.

A dozen ShareX libraries, two solutions, one package version file

The repository is a Visual Studio solution per concern, and the directory names are the architecture: ShareX.ScreenCaptureLib, ShareX.ImageEditor, ShareX.ImageEditor.App, ShareX.ImageEffectsLib, ShareX.UploadersLib, ShareX.HelpersLib, ShareX.HistoryLib, ShareX.Tools, ShareX.Setup, ShareX.Steam, ShareX.NativeMessagingHost, ShareX.Avalonia and the ShareX application itself.

Two details stand out. There are two solution files, ShareX.sln and ShareX.ImageEditor.sln, so the image editor is a separate buildable unit rather than a sub-project of the app. And versions are centralised in Directory.Packages.props alongside Directory.build.props and Directory.build.targets, which is central package management: one file to change a dependency version instead of forty project files.

The rest of the root is the usual .NET furniture, .editorconfig, .gitattributes, .github, .gitignore, .vscode, a Scripts directory and the Licenses folder for third-party notices. Two project names tell you where the edges are: ShareX.Steam is the store build, and ShareX.NativeMessagingHost is a host for another application to talk to ShareX, though the README does not document that surface.

Windows is the platform, and there are four places to get it

The README calls ShareX an application for Windows, and every download route follows from that: the official website at getsharex.com, the downloads page, GitHub releases, the Microsoft Store, and a Steam page. Four channels, which means four different update behaviours, and the portable version is the one to take if you do not want an installer writing to the machine.

The one hint of something else is a directory named ShareX.Avalonia, an Avalonia UI project, in a tree whose published builds are Windows ones. The README does not claim a Linux or macOS release, does not list either platform among the download options, and does not describe what the Avalonia project is for. So for anyone arriving with the question of installing ShareX on Linux, Ubuntu or a Mac, the repository as it stands does not answer it, and the only other signal is the project's own website.

What the README is clear about is provenance, which is the part worth checking before you install: the safest downloads are the official links, and it lists the website, the GitHub repository, the changelog, the privacy policy and a donate page alongside the store listings.

Editorial conclusion

Use ShareX when you are on Windows and you take dozens of screenshots a day for bug reports, documentation or support, because the value is the chain after the shutter rather than the capture itself. Do not reach for it if you need Linux, macOS or screen recording with narration, since the repository describes a Windows application with no audio option in its capture list. Before you build a workflow on it, pick your upload destination deliberately, decide whether the built-in destinations or your own Amazon S3, Google Cloud Storage or Cloudflare R2 bucket suits your data, and note that v21.0.0 shipped on 2026-07-03 while the develop branch has moved on, so a development build is a different thing from the stable release.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository
4. Release notes