Capture-first design
Fullscreen, window, region, freehand, scrolling capture, and more — with optional delay and cursor inclusion for tutorials.
Windows
Free
Open source
Capture · Record · Ship
ShareX — screen capture, recording & sharing
— built for power users
ShareX goes beyond Print Screen: region capture, scrolling screenshots, GIFs, video, OCR, and automated upload workflows. This page summarizes what it does, how people use it in real projects, and how to fix the issues newcomers hit most often.
Note. Independent resource — always verify installers and updates with a source you trust before you run them.
Fig. 1 — ShareX main window (recent captures).
What ShareX is (and why teams still pick it)
ShareX is a long-standing Windows productivity tool for capturing the screen, recording video, and sending results to dozens of destinations. Unlike many “screenshot tools” that only save files locally, ShareX is built around workflows: after capture, you can run steps automatically — watermark, resize, upload, shorten URLs, copy a link to the clipboard, or run a custom command.
Automation & hotkeys
Per-task hotkeys, “after capture” tasks, and folder watching help you repeat the same pipeline hundreds of times a day without thinking.
Community & docs
Active Discord, Reddit, and community write-ups mean obscure edge cases are often documented — great when you’re integrating uploads or custom scripts.
ShareX in screenshots
Real interface shots from the images/ folder: tools, dev builds, color picker, and more.
Features people rely on daily
The list below is not exhaustive — check release notes from wherever you obtain ShareX for version-by-version detail.
- Region & window capture with magnifier and quick re-capture.
- Scrolling capture for long pages — handy for docs and chat logs; see in-app help for options.
- Screen recording to video or animated GIF for bug reports and UI demos.
- OCR to grab text from images when copy/paste is not available.
- Image effects — borders, shadows, watermarks, and more.
- Actions for power users: run programs, send keystrokes, and chain steps.
- CLI arguments for scripting and automation.
- Translations contributed by the community.
- Keybind reference to avoid conflicts with games and IDEs — configure in ShareX hotkey settings.
Capture modes in practice
Choosing the right mode saves time and keeps files consistent — especially when your team shares screenshots in tickets or design reviews.
Region capture for UI bugs
For software issues, a tight region plus a short screen recording often beats a wall of text. Many developers bind region capture to a single key, then let ShareX upload and paste the URL straight into their issue tracker or Jira.
Scrolling capture for documentation
Technical writers and support staff use scrolling capture to archive entire articles or long threads. If a site uses heavy animations, try slowing scroll speed in settings or capture in smaller chunks — that pattern shows up often in community threads.
GIF/video for “it only happens sometimes”
Intermittent glitches are hard to explain. A 5–15 second GIF or MP4 from ShareX can eliminate back-and-forth and is usually smaller than a phone video of a monitor.
Uploads, cloud storage, and custom destinations
ShareX supports many built-in uploaders and “custom uploader” definitions so you can push files to your own infrastructure or CDNs.
Popular cloud paths
- Amazon S3 — common for teams already on AWS.
- Google Cloud Storage — fits GCP-centric orgs.
- Cloudflare R2 — S3-compatible with attractive egress pricing for public links.
Custom uploader basics
If you run a private file API, use ShareX’s Custom uploader editor and in-app guidance. Test with a tiny PNG first; once the response template is correct, the same workflow scales to screen recordings.
Tips from how people actually use ShareX
Patterns below are distilled from common community discussions (Reddit, Discord, forums). Your mileage varies with hardware, GPU drivers, and Windows settings.
-
01
Start with one “happy path” workflow
Pick a single capture type, one destination, and one after-capture task (for example: region → upload → copy URL). Master that before enabling ten hotkeys you will not remember.
-
02
Separate work and personal profiles
If you switch between employer accounts and personal hosting, export settings when they work and keep a backup JSON — it saves hours when you reinstall Windows or move machines.
-
03
Pair OCR with clipboard
Support staff often OCR error dialogs or license keys from screenshots. Combine with “copy text to clipboard” style steps to paste into tickets without retyping.
-
04
Use dev builds only when you need a fix
Bleeding-edge builds can solve a specific bug but may introduce others. Read any notes shipped with pre-release builds before adopting them on a primary workstation.
Troubleshooting & fixes
These are frequent “first checks” when something breaks after an update or driver change.
Hotkeys conflict with games or IDE shortcuts
Open hotkey settings and avoid common game bindings (F keys, Ctrl+Shift combos). Some users scope ShareX to only fire when no fullscreen game is focused, or pause ShareX temporarily from the tray icon.
Upload fails with 403 / auth errors
Regenerate API keys for the destination, confirm the system clock is correct, and re-test with a small file. For S3-compatible providers, double-check bucket policy, region endpoint, and signature version requirements in the provider’s docs.
Black screen or wrong monitor in capture
Multi-monitor setups with mixed scaling sometimes need capture method tweaks. Update GPU drivers, try running ShareX as normal user (not unnecessary elevation), and search community threads for your GPU vendor plus ShareX — workarounds are often documented per driver generation.
Scrolling capture stitches incorrectly
Sites with parallax, sticky headers, or lazy-loaded images confuse automatic stitching. Try slower scroll speed, capture a shorter region, or use classic full-page methods (PDF print) for that specific site.
Frequently asked questions
Is ShareX free?
Yes. ShareX is free and open source (GNU GPL). You can also support the project through donations or by helping with translations and documentation wherever the project publishes those options.
Is ShareX safe?
Download only from sources you trust. Review the publisher’s privacy policy before installing and avoid untrusted “mirror” installers.
Does ShareX run on macOS or Linux?
ShareX targets Windows. Other platforms have different tooling ecosystems; the app’s feature set assumes Windows APIs for capture and shell integration.
Download ShareX
Download buttons go to the official ShareX page on getsharex.com and to GitHub releases. This site does not host the installer.
Installer (setup)
Typical Windows setup package from your trusted source.
Portable ZIP
No install — unpack and run when your source offers a portable build.
Release notes
Read the changelog bundled with the build you download.
More ShareX UI shots: see the Gallery section on this site.
Extended reference
ShareX library — deep, varied, practical
The sections below expand far beyond the summary at the top of this page. Skim the table of contents, jump to what matters, and treat this as a long-form companion for Windows capture workflows — not a substitute for in-app help or your own security review.
Glossary (quick definitions)
- After capture tasks
- Steps ShareX can run automatically right after a capture finishes — upload, copy URL, open editor, run a program, etc.
- Region capture
- You draw a rectangle (or similar) around part of the screen instead of grabbing everything.
- Scrolling capture
- Stitches a tall window or page by scrolling and merging slices; sensitive to site layout.
- OCR
- Optical character recognition — turning pixels of text into selectable characters.
- Workflow
- Your repeatable pipeline from trigger → capture → processing → destination.
- Custom uploader
- Configuration that teaches ShareX how to POST files to your own API or storage.
- Hotkey / task
- A keyboard shortcut bound to one capture or action type.
- Tray icon
- ShareX’s presence near the Windows clock; many quick actions live there.
- History / list
- Recent captures list for reopening files or links.
- Portable build
- Unpacked folder you run without a traditional installer — handy for locked-down PCs if policy allows.
By role — how people actually adopt it
Software engineers
Engineers often start with region capture bound to one key, then add “copy link to clipboard” after upload for tickets. Short GIFs beat paragraphs when UI timing matters. Keep one profile for work and export JSON before OS reinstalls.
For code, consider whether screenshots should include file paths or secrets — crop aggressively. Pair ShareX with your issue tracker’s conventions (naming, attachment limits).
QA & testers
Repro steps love numbered screenshots plus a screen recording for flaky flows. Use delay capture when menus disappear on focus loss. Document expected vs actual in the same ticket thread.
If you file dozens of bugs a week, standardize aspect ratio and cursor visibility so designers scan faster.
Support & success
OCR on error dialogs saves retyping serial numbers and codes. Redact PII before sending externally. Build a personal snippet library of “good” example captures new agents can mimic.
For chat-heavy support, scrolling capture can archive long threads — watch file size before emailing.
Teachers & trainers
Highlight steps with consistent framing so slides stay readable. Record short clips instead of hour-long dumps; students drop off. Check copyright when capturing third-party sites for slides.
Accessibility: prefer large UI text in demos and describe visuals aloud if you share only images.
Design & product
Before/after comparisons are easier when crop windows match. Use lossless PNG for crisp UI; compress later for Slack if needed. Annotate outside the screenshot when possible to keep source clean.
Content & marketing
Social crops differ from documentation crops — maintain separate presets if ShareX supports image effects or post-processing. Keep brand colors consistent when adding borders.
Workflow playbook (mix and match)
- The minimal ticket: region → save to dated folder → attach to ticket manually. No upload dependency.
- The instant link: region → upload → copy URL → paste in chat. Great for fast reviews.
- The tutorial slice: window capture with delay → arrow annotations elsewhere → export PNG.
- The long page archive: scrolling capture → verify stitch → PDF elsewhere if stitch fails.
- The “it flickers” report: 10s screen recording, medium bitrate, trim externally if required.
- The text recovery: OCR → copy to clipboard → paste into notes. Proofread OCR output.
- The privacy pass: capture → blur sensitive zones in an editor → then upload.
- The nightly batch: folder watch → compress → upload to internal bucket (advanced).
- The game clip companion: use ShareX for UI bugs; dedicated GPU capture tools for full-screen performance if needed.
- The compliance pack: local-only saves, no upload tasks, watermark with internal reference ID.
- The teacher pack: consistent 16:9 crop, large cursor, high contrast theme in demo apps.
- The writer pack: grayscale PNG for print-friendly docs, embedded in Markdown via relative paths.
Formats — rough decision table
| Format | Good for | Watch out |
|---|---|---|
| PNG | UI, crisp lines, transparency | Large files for photos |
| JPEG | Photos, smaller attachments | Compression artifacts on text |
| GIF | Short loops, embedded in docs | 256 colors, heavy for long clips |
| WebM / MP4 | Motion, narrated flows | Playback support in target tool |
Security & privacy checklist
- Know whether uploads leave your machine — disable destinations you do not need.
- Strip metadata if your threat model requires it (some editors or exiftool-style steps).
- Redact tokens, emails, patient IDs, and internal URLs before sharing externally.
- Use separate Windows user or profile for highly sensitive work if policy demands separation.
- Verify file hashes when your org requires reproducible installs.
This checklist is educational; your legal, security, and compliance teams override any blog-style advice.
Hardware & performance notes
Screen recording competes with games and IDEs for GPU/CPU. Closing background browser tabs sometimes stabilizes frame times. NVMe disks help when writing large video temp files. RAM matters for long scrolling captures. External 4K displays plus mixed scaling multiply edge cases — test capture methods after display topology changes.
- Laptop on battery: expect thermal throttling to affect recording length.
- Docking stations: reconnect monitors can change which screen ShareX labels as primary.
- Remote desktop: capture behavior may differ from local session — confirm policy.
Accessibility & ergonomics
Keyboard-heavy users benefit from consistent, memorable shortcuts — document them on an index card until muscle memory sticks. For viewers: add alt text when posting screenshots to platforms that support it. High-contrast themes in captured apps improve readability for everyone. Take breaks; rapid capture work is surprisingly taxing on wrists and eyes.
Education & training programs
Run a 30-minute internal workshop: five-minute demo of region vs window, five minutes on history list, ten minutes on “after capture,” ten minutes Q&A. Provide a one-page PDF of hotkeys. Have learners capture one benign internal page and one fake “bug” you planted. Iterate curriculum each quarter as Windows updates shift behavior.
Gaming & overlays
Fullscreen exclusive games may block ordinary capture APIs — community wisdom often suggests borderless window mode for tooling compatibility. Anti-cheat software may interfere; respect game terms of service. For streamers, ShareX can complement (not replace) broadcast software for quick clips to Discord.
Teams & documentation culture
Normalize where screenshots live: wiki, drive, or ticket attachments. Agree on naming `{YYYYMMDD}-{ticket}-{step}.png`. Run occasional audits for PII in public channels. Celebrate concise visuals in code review — they reduce rework.
Myth vs fact (informal)
- Myth: “One hotkey should do everything.” Fact: Specialized hotkeys reduce mistakes.
- Myth: “Scrolling capture always works.” Fact: Modern web layouts break naive stitching.
- Myth: “GIF is always smallest.” Fact: Short video often wins for complex motion.
- Myth: “OCR is perfect.” Fact: Always spot-check critical strings.
File naming & folders
Patterns like project_issue_step.png beat Screenshot (37).png in shared drives. Rotate old captures quarterly. Keep “inbox” and “published” folders separate if you curate tutorials.
OCR strategies
Zoom the source UI before OCR when text is small. Prefer high contrast. For tables, OCR may jumble columns — capture wider context or transcribe manually. Languages: verify the engine matches the document alphabet.
Video & GIF trade-offs
GIF shines for under-15-second UI loops embedded in README files. Video fits narrated walkthroughs and variable frame rates. Consider audio: mute default mic if office noise leaks. Trim dead air in post when file size matters.
Clipboard & automation
Chaining “copy image to clipboard” with paste in Figma, Slack, or email is faster than saving manually — until clipboard managers fight you. Some apps prefer file drops over raw bitmap paste; know your target.
Realistic scenarios (composite)
Scenario A. A payroll analyst screenshots an error, OCRs the code, pastes into an internal wiki, and links the image for designers. Time saved: several minutes per ticket, hundreds per year.
Scenario B. A mobile developer captures mixed-DPI Android emulator windows, crops consistently, and attaches to a regression doc. Reviewers approve faster.
Scenario C. A moderator archives a volatile forum thread via scrolling capture before deletion policy kicks in — legal reviews the archive offline.
Compliance-minded capture
Regulated industries: map where images rest (disk, RAM, cloud). Data retention schedules may apply. Attorney-client privilege contexts may forbid certain uploads altogether. When in doubt, capture locally and let counsel approve distribution.
Remote & hybrid work
Video calls: be careful capturing others’ faces or home backgrounds without consent. Prefer sharing application windows only. VPN latency can slow uploads — queue large files for off-peak if polite on corp networks.
DPI, scaling & multiple monitors
125% vs 150% scaling across monitors produces different pixel dimensions. Teach teammates to mention scale settings when reporting “layout bugs.” Region math in tutorials should avoid hard-coded pixel counts.
Network & uploads
Corporate proxies sometimes block unknown hosts — test uploaders on corp Wi-Fi before promising a workflow. Retry logic and user-visible errors reduce helpdesk tickets. Consider bandwidth: 4K recordings and hotel Wi-Fi do not mix.
Color & accuracy
Design reviews involving brand colors may need calibrated displays — screenshots are not a color proof. Night light / f.lux shifts white point; mention if you capture warm-tinted UI.
Keyboard-first habits
PrintScreen overrides, game launchers, and IDE chords collide. Maintain a personal cheat sheet. Consider layers: rare tasks on Ctrl+Alt combos, frequent tasks on single function keys if unused.
Reducing clutter & noise
Disable notification badges in demos. Close unrelated tabs — they distract readers and leak titles. Use single-window captures when possible.
Quality bar
A “good” capture answers: what app, what state, what action, what outcome — without paragraphs. If viewers ask clarifying questions, your crop failed. Iterate.
After capture
Rename immediately while context is fresh. Tag in your notes tool. If you upload, verify the link in a private window. Delete scratch captures that contain secrets.
Sharing etiquette
Ask before posting screenshots of private chats. Crop coworker names from informal Slack screenshots when posting publicly. Credit designers if you share their mockups.
Lightweight metrics (optional)
Teams sometimes count “tickets closed faster after visual repro policy” — informal surveys beat heavy instrumentation. Do not collect personal data without governance.
Backing up settings
Export JSON after you nail a workflow. Store in password manager attachments or encrypted drive. Version-control sanitized configs if your team shares baseline setups — strip secrets first.
Multiple PCs
Laptop vs desktop: paths in custom tasks may differ — use environment variables where possible. Re-map hotkeys if keyboard layouts change between machines.
Rough timeline perspective
ShareX’s ecosystem matured across many Windows generations — behaviors shifted with compositor, HDR, and per-monitor VRR features. Treat old forum posts as hints, not laws; reproduce on your build.
Extra Q&A style notes
Should I run as administrator? Usually unnecessary; elevation widens blast radius if something goes wrong.
Can I script captures? Many users chain CLI-style invocation with other tools — test on a VM first.
Does dark mode matter? For readability in tickets, yes; for file size, slightly.
What about HDR screenshots? Viewers on SDR displays may see shifted colors — note HDR in ticket text.
How to read this library
You do not need to read top to bottom. Pick a role section, adopt one playbook item this week, then revisit security and naming when you onboard teammates. Content here is meant to be different from the short summaries above: longer, more varied, and opinionated in a practical sense — still not official guidance from any vendor.