Speed
Assign different hotkeys per capture mode. After capture, auto-save to a folder, run OCR, or open the image editor without hunting through menus.
01 — Intro
Windows · Open source · Free forever
ShareX: capture, annotate, and automate your screen workflow
ShareX is a powerful screen capture and productivity suite for Windows. This guide explains what to install first, how capture and upload fit together, and where to look when something breaks. Jump to workflows, troubleshooting, or the FAQ; use the download section for the current Windows build linked on this page.
- Region, window, fullscreen, and scrolling capture
- Built-in editor, effects, and color tools
- Custom uploaders (S3, R2, Imgur, your server)
- Hotkeys, tasks, and command-line automation
Illustrative imagery from the community.
03 — Features
Feature overview
The following sections mirror how documentation and long-time users describe the product. For release notes, see what ships with each new build or the download section on this page.
Main window & history
The list view shows recent workflows—helpful when you need to re-open a file, re-copy a URL, or verify which uploader ran. Filters and search reduce time spent digging through download folders.
On-screen color picker
Designers and front-end developers use the picker to grab hex/RGB values from anywhere on screen, with history for comparing shades across apps and browsers.
Effects & beautify
Watermarks, borders, shadows, and other image effects help keep screenshots consistent for docs and social posts.
Flexible capture modes
Combine rectangle, window, and monitor targets with optional delay and cursor inclusion—common when capturing dropdowns or modal dialogs.
04 — Workflows
Workflows that scale
ShareX “tasks” connect capture types to post-capture steps. Below are patterns people reuse across teams once hotkeys and destinations are configured. When uploads, hotkeys, or capture modes misbehave, continue with troubleshooting.
Support & IT
Capture error dialogs, blur sensitive pixels in the editor, upload to a private bucket, paste the link into a ticket. Pair with scrolling capture for long logs.
Design & QA
Region capture with pixel-perfect dimensions, step annotations, and consistent file naming for regression folders.
Content & education
Record clips or GIFs, trim in external tools if needed, and push to a CDN-backed uploader for fast embeds.
Developers
OCR for copying text from images, custom uploaders for internal APIs, and CLI arguments for scripting alongside CI screenshots.
Scrolling capture
Long pages and chat threads are easier to archive when scrolling capture stitches content vertically. Browser quirks and timing vary—check in-app help and community threads for current behaviour.
05 — Community
What users commonly report
These are recurring themes from forums, Discord, and Reddit—not paid endorsements. They explain why ShareX stays installed after people try lighter tools.
“I replaced three utilities—snip, a GIF recorder, and a separate uploader—with one hotkey stack. The learning curve is real, but after exporting my settings to a file, onboarding a new PC takes minutes.”
Paraphrased pattern from community discussions
“Custom uploaders felt intimidating until I copied a template from the docs. Now screenshots land in the same bucket as our app assets, with predictable URLs for markdown docs.”
Typical workflow described by self-hosters
Less context switching
Keep hands on the keyboard: capture, annotate, upload, and paste a link without opening a browser uploader tab each time.
Portable setups
Some teams distribute the portable ZIP on locked-down machines where installers are restricted—verify policy with IT first.
Extensive docs
Keybind reference, OCR tuning, translation contribution, and dev builds are covered in bundled help and project documentation.
06 — Fixes
Troubleshooting & fixes
Quick answers to problems that show up often in search and community channels. When in doubt, update to the latest stable build and read the release notes bundled with the installer.
▸ Hotkeys do nothing / another app stole them
Open ShareX hotkey settings and look for conflicts (Discord, GPU software, and IDE shortcuts often overlap). Windows 11 “Copilot” and OEM utilities may also bind Print Screen. Reassign or disable the conflicting shortcut in the other program.
▸ Upload fails with 403 / signature errors (S3, R2, etc.)
Double-check bucket policy, region endpoint, and clock sync on your PC. For S3-compatible providers, confirm the custom uploader JSON matches their required headers. See provider docs for Amazon S3 and Cloudflare R2.
▸ Black screen when recording some games or protected content
DRM and exclusive fullscreen can block capture. Try borderless window mode, a different capture method, or the game bar as a fallback. Results depend on the title and GPU driver.
▸ OCR accuracy is poor on small or low-contrast text
Zoom the target UI before capture, increase contrast, or capture a larger region. In ShareX, open OCR settings to adjust language packs and recognition options.
▸ Antivirus quarantined ShareX or blocked hooks
Screen capture tools use low-level hooks that some heuristics flag. Verify the binary against a signed build from a trusted source, allowlist the install folder, and avoid unknown repackaged builds.
Trying dev builds
Preview builds can fix regressions early but may introduce new ones. Read the preview build notes carefully before deploying on production machines.
07 — Tips
Power-user tips
- 1Export your configuration after a good setup—backup
Documents\ShareXor use in-app backup options so reinstalls are painless. - 2Name patterns with date and window title variables keep screenshots sortable for audits and design iterations.
- 3Combine with CLI using command-line switches documented in ShareX help for scripted captures in automation.
- 4Learn one new tool per week—hash check, ruler, or DNS tools—so the “Tools” menu becomes a toolkit instead of clutter.
- 5Review keybinds quarterly as your stack changes; stale shortcuts are a top reason people think ShareX “broke.”
ShareX vs. basic snipping tools
Windows Snipping Tool and Snip & Sketch are fine for one-off clips. ShareX wins when you need repeatable post-capture actions, historical task list, scrolling capture, or custom upload destinations. Greenshot and PicPick overlap partially; your choice depends on editor preferences and uploader ecosystem.
08 — Download
Download ShareX
Direct downloads below target release v19.0.2 (March 2026 refresh of this page). When ShareX ships a newer build, we update these links—if a file 404s, retry later or contact the source you obtained ShareX from.
09 — FAQ
Frequently asked questions
Is ShareX free for commercial use?
ShareX is open-source software; review the license bundled with the project for your compliance needs. This site is an independent guide and not affiliated with the core maintainers.
Does ShareX run on macOS or Linux?
ShareX targets Windows. Other platforms have different tooling (e.g., Flameshot, Ksnip). Running on Linux typically requires Wine or a VM with mixed results.
How do I contribute translations?
See ShareX documentation for how to contribute translations and localize the UI.
10 — Deep reference
Extended library — 33 topics
This block sits below the main guide and multiplies practical depth with thirty-three standalone notes—each different in angle (workflow, privacy, hardware, integrations, edge cases). Skim headings or search the page for keywords.
01 / 33
After-capture action chains
Order matters: copy to clipboard before upload if you need instant paste, or upload first when the link is what colleagues expect. Duplicate pipelines for “internal blur” vs “public crop” so you never apply the wrong mask.
02 / 33
Watch folders & folder uploaders
Pair a dedicated “inbox” directory with a task that fires when new PNGs arrive—useful for scanners or exports from design tools. Keep paths short to avoid path-length issues on older network shares.
03 / 33
Clipboard upload & monitor
When the source is already an image in RAM, skip disk round-trips: push straight to your uploader and log the URL in history. Watch for huge clipboard bitmaps from 4K screens—they can spike memory briefly.
04 / 33
Recording codecs & containers
H.264 remains the safest default for compatibility; HEVC can shrink files but may stutter on older editors. If audio drifts, check sample-rate mismatches between game output and system devices.
05 / 33
GIF timing & palette
Lower frame rates keep GIFs under email limits; for UI micro-interactions, 8–12 fps is often enough. Flat UI with few colors compresses best—gradients explode file size.
06 / 33
Watermark templates
Use semi-transparent PNG marks for brand consistency; anchor to corners so ultrawide crops still look intentional. Version your watermark file name when marketing refreshes logos.
07 / 33
URL shorteners & branded links
If your org runs a shortener API, wire it after upload so tickets stay tidy. Avoid public shorteners for sensitive previews—expiry and analytics vary unpredictably.
08 / 33
QR decode & encode workflows
Capture a QR from a projector slide and run decode to paste the URL faster than typing. For outbound, embed Wi-Fi or cal-link QR in docs—verify scan distance with a phone before publishing.
09 / 33
EXIF & metadata hygiene
Screenshots can inherit color profiles or timestamps you did not intend. Strip metadata for public posts when paths or machine names might leak; keep originals internally for forensics.
10 / 33
Mixed-DPI multi-monitor
Per-monitor scaling can shift coordinates for region capture after sleep/resume. If edges look “off by one,” toggle GPU scaling or re-align monitors in Windows display settings.
11 / 33
High refresh & vsync
Recording at 360 Hz panels may produce enormous files; cap capture FPS in settings when you only need 60 fps narrative. G-Sync/FreeSync rarely breaks capture, but exclusive fullscreen still surprises some titles.
12 / 33
Game capture fallbacks
When hooks fail, borderless windowed mode plus display capture often works. Anti-cheat software may block everything—document that limitation for streamers on your team.
13 / 33
Print Screen & OEM overrides
Laptop Fn rows sometimes remap PrtSc; vendor utilities may intercept before ShareX sees the key. Map a rare combo (e.g., Ctrl+Alt+Shift+S) for zero conflict.
14 / 33
Startup & session policies
Delayed start reduces boot contention on HDD laptops. On shared PCs, prefer portable mode with settings beside the binary so user profiles stay clean.
15 / 33
Installed vs portable paths
Installers register shell extensions; portable builds skip that but travel on USB. Point both at the same custom uploader JSON via a shared network path if you want identical behaviour.
16 / 33
Migration checklist
Export hotkeys, uploaders, and personal path rules before OS upgrades. Verify destination credentials separately—tokens in custom scripts may be device-scoped.
17 / 33
Two-PC sync without cloud
Robocopy or git-LFS a folder of JSON configs during maintenance windows. Never sync while the app is writing settings—close ShareX first to avoid corruption.
18 / 33
Browser-adjacent workflows
Full-page captures of SPAs may need scrolling capture instead of one-shot viewport. Disable lazy-load thrash by scrolling slowly so stitched frames align.
19 / 33
Drag-drop & shell integration
Dropping a file onto the main window can trigger a configured uploader task—handy for batching exports from Figma. Confirm file type filters so PDFs do not hit image-only pipelines.
20 / 33
History limits & disk hygiene
Cap history rows or age so SSD journals stay small on laptops. Pair with a monthly folder archive job for compliance-heavy teams.
21 / 33
Upload size & timeout tuning
Corporate proxies may kill long uploads—chunked APIs or multipart uploads (when supported by your uploader) reduce failure rates. Retry with exponential backoff in custom scripts.
22 / 33
Thumbnails & cache folders
If the main window feels sluggish, clear thumbnail caches during downtime. Store caches on local SSD—not network drives—for snappy scrolling.
23 / 33
Editor: shapes & pixel snapping
Hold modifier keys (per in-app help) for straight lines and fixed aspect ratios. Snap to edges when annotating mockups so arrows align to the grid you are critiquing.
24 / 33
Redaction: blur vs pixelate
Pixelate is reversible at small block sizes—use solid fills for IDs. Gaussian blur still leaks structure on high-contrast text; combine with crop when possible.
25 / 33
Cursor spotlight & click rings
Tutorials benefit from visible cursor emphasis; keep rings subtle so viewers focus on the UI. Test on both light and dark themes before publishing.
26 / 33
Screen ruler & alignment
Measure padding disputes between design and engineering with on-screen rulers instead of screenshots pasted into image editors. Screenshot the ruler overlay if you need async review.
27 / 33
DNS & network tools (support)
When “upload works here but not there,” quick DNS lookups from the same machine isolate split-horizon issues. Document resolver IPs in tickets alongside traceroutes.
28 / 33
Hash verification habit
Before circulating a build internally, hash the installer and publish the digest beside the file. Reduces “did this get corrupted on USB?” debates.
29 / 33
Monitor test patterns
Dead pixels and banding show up in solid colors—capture test slides for RMA evidence. Note panel model and firmware in the ticket text.
30 / 33
FTP / SFTP destinations
Legacy intranets still speak FTP; prefer SFTP or FTPS when available. Rotate passwords in both ShareX and the server config on the same change ticket.
31 / 33
Email & SMTP handoff
For low-tech stakeholders, emailing captures can beat link sharing—watch attachment limits and virus-scan delays on outbound gateways.
32 / 33
Webhooks & automation glue
POST JSON to internal bots when a screenshot lands—drive Slack threads or ticket prefills. Sign payloads with a shared secret so random URLs cannot spam your channel.
33 / 33
Accessibility & color contrast
When annotating for WCAG reviews, use high-contrast arrows and avoid red–green only distinctions. Mention if the capture is sRGB vs wide-gamut so reviewers interpret colors correctly.
Quick comparison — capture intent
| Goal | Typical mode | Watch out for |
|---|---|---|
| Bug report | Region + arrow notes | Sensitive data in background |
| Release notes | GIF or short MP4 | Codec compatibility on Mac viewers |
| Legal hold | Lossless PNG + hash | Chain of custody metadata |
| Design critique | Pixel grid + color pick | Display scaling skew |
- Glossary — task
- A saved pipeline linking a capture type (or source) to ordered actions such as save, upload, and copy URL. Tasks are what you duplicate when onboarding teammates.
- Glossary — destination
- The configured endpoint for an upload—cloud bucket, custom HTTP, or script. Destinations fail independently; keep a “local only” fallback task.
▸ Checklist: first week with ShareX
- Set one “daily driver” hotkey and one backup combo.
- Pick a single uploader and test with a harmless image.
- Export settings after anything works—celebrate with a backup file.
- Add blur/redact task before you screenshot production data.
▸ Checklist: before a major Windows update
- Export ShareX settings and note your install type (setup vs portable).
- Screenshot your hotkey screen—human-readable insurance.
- Verify custom uploader credentials still work after reboot.
- Least privilege: run with normal user rights; escalate only when a tool explicitly requires it.
- Link hygiene: prefer expiring links for internal previews when your storage supports TTL.
- QA habit: open your own upload URL in an incognito window before pasting into a client email.
“The best ShareX setup is the one your future self can re-create from a single exported file and a short README—everything else is improvisation.”
11 — Field guide
Expanded manual — five layers
This zone sits under the deep reference block. It is structured as five independent layers—each layer uses a different layout and fresh topics so nothing repeats the 33-card library above.
Layer 1 — Scenario lab
Ten bite-sized situations you can map to tasks and hotkeys. None duplicate the reference cards.
S01
Remote stand-up: capture a single IDE error line, blur the repo path, upload to the team bucket, paste in chat within ten seconds.
S02
Teacher recording: freeze a slide region, annotate with the pointer path, export PNG for the LMS—avoid full-screen video when bandwidth is poor.
S03
SOC triage: hash a suspicious dialog PNG before sharing externally; keep raw capture in a case folder with ticket ID in the filename.
S04
Sales demo: pre-stage a “clean” browser profile, capture region-only UI, strip bookmarks bar for a polished deck insert.
S05
RDP session: capture the remote desktop window, not the local shell—note DPI scaling so ticket readers do not misread pixel widths.
S06
Citrix published app: window capture beats fullscreen when the session chrome differs from native Windows.
S07
Battery-powered laptop: prefer still captures over long recordings on flights; defer GIF creation until wall power returns.
S08
VPN split tunnel: verify which interface a browser uses before capturing “public IP” evidence for networking tickets.
S09
Accessibility audit: capture focus rings and contrast side-by-side; log browser zoom level in the ticket body.
S10
Archive handoff: bundle PNG + JSON export of uploader config (redacted) so the next admin knows how URLs were formed.
Layer 2 — Extra FAQ (accordion)
▸ Can ShareX replace OBS for streaming?
ShareX excels at clips and GIFs, not full multi-scene streaming. Use dedicated streaming software for overlays, bitrate ladders, and chat integrations.
▸ Why does my cursor look offset in captures?
Scaling above 100%, custom cursor themes, and remote sessions can shift appearance. Test with default cursor and 100% scaling to isolate the cause.
▸ Is clipboard history from ShareX a security risk?
Any tool that logs history can retain secrets. Clear history on shared machines and avoid copying passwords into workflows that auto-upload.
▸ How do I document steps without drowning in files?
Use one folder per article, numbered filenames, and a single GIF when motion matters—reserve PNG sequences for accessibility-friendly static fallbacks.
▸ Will ShareX work inside Windows Sandbox?
Often yes for basic capture, but hooks and drivers differ. Treat sandbox captures as best-effort, not parity with bare metal.
▸ What about HDR displays and washed-out screenshots?
HDR content can look flat in SDR captures. Toggle HDR off temporarily for documentation shots, or note HDR in the caption for reviewers.
▸ Can I run ShareX from a read-only network share?
Portable binaries may start, but settings and temp files expect writable paths—redirect personal folders to a writable profile location.
▸ How do teams standardize without a central MDM?
Publish a signed settings export, a one-page “allowed uploaders” policy, and example tasks. Rotate credentials on a schedule, not ad hoc.
▸ Does antivirus slow down screen recording?
Real-time scanning can add jitter. Add exclusions only after risk review—prefer corporate allowlists over blanket disable.
▸ Where does ShareX fit next to Snipping Tool in Windows 11?
Snipping Tool is fast for casual clips; ShareX wins when history, uploaders, and batch actions are non-negotiable.
Layer 3 — Naming patterns & paths
Example filename templates (adapt to your rules)
{yyyy}-{MM}-{dd}_{HH}-{mm}-{ss}_{processname}
ticket-{TicketId}_v{rev}_step{nn}.png
{unix}-monitor{index}-w{width}px.png
Folder layout ideas
- •
.\captures\YYYY\MM\for chronological archives - •
.\by-project\{slug}\when work spans weeks - •
.\staging\for redacted exports only
| Symbol | Typical meaning | Gotcha |
|---|---|---|
| {width} | Capture width in pixels | Changes with DPI per monitor |
| {unix} | Unix timestamp | Sort-friendly globally |
| {processname} | Active process | May be empty or generic |
Layer 4 — A workday timeline (illustrative)
-
AM
09:00 — Stand-up evidence
One region grab of the sprint board; upload to internal wiki; link in meeting notes.
-
AM
11:30 — Bug reproduction
GIF of the interaction; separate PNG of the stack trace with secrets blurred.
-
PM
14:00 — Design review
Side-by-side captures with color picker readouts attached in Figma comments.
-
PM
16:30 — Support escalation
Scrolling capture of logs; hash file archived next to the ticket export.
-
EOD
17:45 — Hygiene
Clear staging folder; verify no PII in today’s upload history; backup settings if you changed tasks.
Layer 5 — Roles & mini recipes
Product manager
- Capture competitor flows as GIF with cursor visible.
- Keep a “redacted” task for customer screenshots.
SRE / ops
- Pair PNG evidence with traceroute text in the ticket.
- Use consistent UTC timestamps in filenames.
Technical writer
- Number figures to match heading depth in docs.
- Store source captures beside the markdown repo.
QA engineer
- Build a regression folder per release branch.
- Use region presets for repeated viewport sizes.
Compliance officer (high level)
Map which uploaders are approved, where data residency lives, and how long URLs remain valid. This site does not provide legal advice—treat captures like any other data class.
