Upload Screenshots Instantly Using ShareX, Flameshot, or Greenshot

Taking a screenshot is instant. Getting it somewhere you can share is usually not. Save the file, open a browser tab, find the upload button, wait for it to finish, copy the link, close the tab. For anyone who screenshots more than a few times a day, that gap between capture and shareable link adds up to real friction. It is also exactly the problem YourImageShare's screenshot tool integrations exist to remove.

ShareX, Flameshot, and Greenshot are three of the most widely used screenshot tools on Windows and Linux, and all three support sending a capture straight to a custom upload destination the moment you take it. Point any of them at YourImageShare and the browser tab disappears from the workflow entirely: capture, upload, link copied to your clipboard, done.

ShareX (Windows)

ShareX is probably the most feature complete screenshot and screen recording tool on Windows, and its custom uploader system is exactly built for services like this one. A ready-made .sxcu configuration file is available on the API documentation page, under Screenshot Tools. Download it, then in ShareX go to Destinations, Custom uploader settings, Import, from file, and open the downloaded file. Replace the placeholder API key in the Headers field with your real one, set it as your active image and file destination, and every capture from that point on uploads automatically the moment you take it, with the resulting direct link copied to your clipboard ready to paste.

One thing worth knowing: ShareX's own built in deletion shortcut is not wired up in this configuration, since it expects a simple link based deletion request and this API's delete endpoint is a proper authenticated request instead. Deleting an upload made through ShareX is a quick trip to My account on yourimageshare.com, or a call to the delete endpoint directly if you are comfortable with the API.

Flameshot (Linux)

Flameshot is the default screenshot tool on a lot of Linux desktops, and while it does not have ShareX style built in custom uploaders, a small shell script fills the same role. The script runs flameshot gui to let you select an area, uploads the result, and copies the returned link to your clipboard using whichever clipboard tool is available on your system, falling back gracefully if one is missing. Setup is a one time thing: download the script, make it executable, and set your API key as an environment variable or in a config file. From then on, bind the script to whatever keyboard shortcut you currently use for Flameshot, and every capture becomes a capture-and-upload in one keystroke.

Greenshot (Windows)

Greenshot is a lighter, simpler alternative to ShareX that a lot of people prefer specifically because it stays out of the way. It supports external command destinations, and a PowerShell script handles the actual upload, written against the version of PowerShell that ships with Windows so there is nothing extra to install. Setup means telling Greenshot's External command destination to run PowerShell with the script as an argument, and setting your API key once as an environment variable. After that, Greenshot's normal capture flow just works, with the upload happening silently in the background.

Why bother with any of this over just dragging a file into a browser tab

The honest answer is speed and habit. If you screenshot a handful of times a week, a browser tab is fine. If you screenshot dozens of times a day, whether that is documenting bugs for a development team, capturing something to send a colleague, or building a knowledge base full of annotated screenshots, the browser tab becomes the slowest part of an otherwise instant action. Wiring the upload directly into the tool you already use to capture the screenshot removes an entire manual step, and once it is set up once, it stays set up. There is no ongoing maintenance, no login screen to click through, nothing to remember except the keyboard shortcut you already know.

What happens to the uploaded file afterward

Anything uploaded through one of these integrations behaves exactly like a normal upload made through the website: it gets a direct file URL, a page link with sharing options, an embeddable HTML tag, and a BBCode link for forums, all generated automatically. If a particular screenshot only needs to exist for a little while, like a one time bug report or a temporary support attachment, the same expiring uploads feature available through the API can be applied, so the file and its page quietly disappear on their own after a set time rather than needing manual cleanup later. Full details on how expiry works are on the API reference.

Building your own integration

ShareX, Flameshot, and Greenshot cover the most common screenshot tools, but the underlying mechanism is just the same upload API documented at yourimageshare.com/about/api. Any tool that can run a script or make an HTTP request on a keyboard shortcut can be wired up the same way. Official client libraries exist for JavaScript and Python if you would rather write a small script than work with raw curl commands, and both handle the multipart upload and error parsing for you rather than leaving you to build it from scratch.

Getting started

All three downloads, along with the exact setup steps for each, are on the API documentation page under Screenshot Tools. You will need an API key first, which takes under a minute to generate from My account once you are signed in at yourimageshare.com. No credit card, no trial period, the free tier is generous enough that daily screenshot habits fit comfortably inside it.

Getting the API key field right the first time

The most common setup mistake with any of these three tools is a stray space or an incomplete paste when replacing the placeholder API key, which produces a confusing authentication error on the very first capture rather than anything obviously pointing at the real cause. After setting up any of the three, take a capture immediately and confirm a real, working link shows up, either copied to your clipboard or visible in the tool's own history. If it fails, the API key field is the first thing worth double-checking, followed by confirming the key itself is still valid by checking the API tab in My account on yourimageshare.com, since a regenerated key immediately invalidates the old one.

Using a different screenshot tool

ShareX, Flameshot, and Greenshot cover the most common setups on Windows and Linux, but they are not the only screenshot tools that support custom upload destinations. Anything that can run a script or send an HTTP request after a capture can be pointed at the same upload endpoint. The requirements are simple: a POST to /api, the file sent as multipart form data in a field named uploads, and your API key either as a header or a query parameter. If your screenshot tool of choice supports a custom command or webhook after capture, the same pattern used in the Flameshot and Greenshot scripts, reading a file path and uploading it, adapts directly. Full field-by-field details are on the API documentation page.

Mac users

None of the three tools covered here run natively on macOS, but the same underlying idea works with whatever screenshot workflow you already use, most commonly a small Shortcuts automation or a script bound to a keyboard shortcut using launchd or a menu bar utility. The Flameshot shell script is a reasonable starting template even outside Linux, since the actual upload step, a curl request with the file attached, works identically on macOS. Adjusting the clipboard copy step to use pbcopy instead of the Linux clipboard tools is generally the only change needed.

What a good screenshot workflow actually looks like

It is worth being specific about what "instant" means here, since the phrase gets used loosely. With any of these three integrations set up correctly, the full sequence from pressing a capture shortcut to having a working link on your clipboard is a single, uninterrupted action: select the area, release the mouse, and the link is already there waiting to be pasted. There is no intermediate save dialog, no folder to remember, no browser window to switch to. That single detail, removing every step between capture and shareable link down to zero, is the entire point, and it is also why so many people who set one of these up once never go back to the old way.

For anyone documenting bugs as part of a job, this adds up faster than it might seem. A handful of screenshots a day, each saving even thirty seconds over the old save-and-upload routine, is real time back over a working week, without changing anything else about how the work gets done.

Keeping screenshots organized once there are a lot of them

Once uploading is this frictionless, the number of screenshots taken tends to grow quickly, which raises a fair question: does anything get lost in the shuffle. Every upload, however it arrived, whether through the website, a script, or one of these tools, is listed in My account on yourimageshare.com, newest first, with a title and description you can add after the fact if a particular screenshot is worth keeping track of. Anything only needed briefly can be given an expiry at upload time instead, so old, no-longer-useful captures do not need to be manually cleaned out later.

One key, multiple machines

If a screenshot workflow spans more than one computer, a work laptop and a personal desktop, for instance, the same API key can be reused across both without any conflict. Uploads from either machine land in the same account and show up together in My account, so there is no need to generate a separate key per device unless you specifically want to track usage separately or plan to revoke access to one machine independently later.

Set aside the ten minutes it takes to configure whichever tool matches your setup, and the payoff compounds every single time a screenshot gets taken from that point forward, for as long as the tool stays installed.

If screenshots are not the main thing being uploaded, a companion post on this blog covers automating uploads directly through the API for scripts, bots, and build pipelines, and another covers adding a real upload button to forum software like phpBB, SMF, and MyBB, for anyone running a community rather than just uploading personally.

Either way, the goal is the same one the rest of YourImageShare is built around: get the file hosted and the link in hand as fast as possible, with as little in between as possible.

Set one of these up once and the habit sticks on its own, since the faster path is also simply the easier one to keep using.

Prefer a browser extension over a desktop app? YourImageShare Capture for Firefox covers the same ground - capture, annotate, and publish - without leaving the browser.