Screenshot tools and scripts

The screenshot tools in Profile require both tokens.manage and files.upload. Managing or downloading credentials uses tokens.manage; performing an upload also requires files.upload. Your account’s roles apply even to previously downloaded configurations. Removing upload permission stops their authenticated uploads without changing the credential. The Use this profile in your tools buttons on a saved upload profile follow the same rule.

Capture, upload, and copy a link without opening your browser. Profile → Uploads → Screenshot tools and scripts provides ready-to-use downloads for common capture tools and a general Bash uploader.

You do not need to create or manually paste an API key for these downloads. Flare includes your account upload token automatically.

Download a configuration or script with your instance address and upload credential already included.

Download a configuration or script with your instance address and upload credential already included.

Choose your tool

Your workflow	Flare download
Capture and upload on Windows	ShareX .sxcu configuration.
Screenshots and recordings on macOS	iTake .itup configuration.
Annotated screenshots on Linux	Flameshot Bash script.
Screenshots and recordings on KDE	Spectacle Bash script.
Upload an existing file from a terminal	General Bash script.

Each download is named after your account name, for example alex-morgan-sharex.sxcu, alex-morgan-flameshot.sh, or alex-morgan-spectacle-recording.sh.

For a particular sharing workflow, download the client from a saved upload profile instead of the general tools section. General downloads follow account defaults; profile downloads explicitly select that profile. Flameshot, Spectacle, and iTake open the same setup dialog there.

Downloads contain a credential

Keep these configurations and scripts private. Do not commit them to a public repository or attach them to a support issue without removing the token. Anyone with a working credential may be able to use the access it grants. Flare sends every download with Cache-Control: private, no-store, so browsers and proxies don't cache a copy. Delete downloaded files you no longer use.

ShareX on Windows

1. Install and open ShareX.
2. In Flare, open Profile → Uploads → Screenshot tools and scripts and download the ShareX configuration.
3. Open the downloaded .sxcu file to import it into ShareX.
4. Select the imported custom uploader for the relevant file or image destination in ShareX.
5. Capture or upload a small test file, then open the returned link.

ShareX controls which captures upload and which after-upload actions run. Enable its copy-URL action if you want the link placed on your clipboard. Flare's configuration supplies the upload endpoint and response parsing; see the ShareX custom uploader documentation for the tool's destination and import controls.

If you want different behavior for different tasks, create profiles such as Public screenshots and Temporary clips, then download the configuration for the appropriate profile.

iTake on macOS

iTake is an open-source menu-bar capture application for screenshots and screen recordings. Its published requirements are macOS 15 or later on Apple Silicon or Intel.

1. Install iTake using its installation instructions, open it, and allow screen-recording access when prompted.
2. In Flare, choose Set up iTake → Download config. To select a particular upload profile, use that profile's iTake action instead.
3. Open the .itup download and confirm import in iTake.
4. In Preferences → Uploader, select Flare — Account defaults or the named Flare profile.
5. Enable Upload Automatically and keep Auto Copy Link enabled for automatic sharing.
6. Capture a screenshot or finish a recording. If iTake requests access to its uploader credential in Keychain, approve it so uploading can proceed.

Both images and recordings still follow your Flare upload limits, visibility, and expiration choices. If you change your instance address or replace the account upload token, remove the old uploader and import a fresh Flare configuration.

Flameshot on Linux

Choose the Flameshot Download script action, set its two switches, and download the generated Bash script:

• Wayland clipboard support copies the link with wl-copy instead of xsel.
• Hyprland compatibility sets XDG_CURRENT_DESKTOP=sway before capturing. Flameshot doesn't detect Hyprland, and this is the usual workaround.

The generated script checks for flameshot, curl, jq, and its clipboard tool: xsel, or wl-copy with Wayland clipboard support. The dialog lists the same commands for the options you choose. Follow the installation notes at the top of the file, then run it with Bash:

bash ./your-flameshot-script.sh

You can also make the file executable and bind its path to a desktop keyboard shortcut. Keep the script in a private location because it contains the upload token.

Flare's generated Flameshot script supports Linux only. Use the iTake integration for the documented macOS capture workflow.

Spectacle on KDE

Open Spectacle's Download script action and select Screenshot or Screen recording.

Screenshot choices are full desktop, current monitor, active window, or a selected region. A recording covers a selected region or, with Current monitor recording, the whole screen under the pointer. Earlier versions also offered Full desktop recording, which made the same recording; scripts downloaded with it keep working. A Profile page opened before the upgrade may still offer it and refuse the download; reload the page and choose Current monitor recording. The form also offers Wayland clipboard support and an option to include the mouse pointer. Reset options returns every choice to its default, the script type and modes included. Earlier versions reset what the script would use but kept showing the previous script type and mode.

The generated script checks for spectacle, curl, jq, and its clipboard tool: xsel, or wl-copy with Wayland clipboard support. Read the script's setup notes, then run it with Bash. The available capture and recording behavior also depends on your installed Spectacle version and desktop session.

Choose the capture mode and desktop environment before downloading the Spectacle script.

Choose the capture mode and desktop environment before downloading the Spectacle script.

Bash: upload any file

Download the general Bash script to send an existing file from the terminal. It requires curl, jq, and file.

Run the actual filename you downloaded, passing a path to one file:

bash ./your-flare-script.sh ./screenshot.png
bash ./your-flare-script.sh "./recordings/product demo.mp4"

The script prints the share-page URL. It also tries available clipboard utilities: wl-copy, xsel, xclip, or pbcopy. If none is available, copy the printed URL manually.

This script uses a regular multipart upload. It is useful for simple terminal uploads; it does not provide the browser's chunked-upload workflow or a resumable transfer interface. For a more specialized integration, see the API guide.

Account upload token and named tokens

The account upload token is created for you and included in generated downloads. The tools section lets you reveal, copy, or Replace token when you need to configure a tool manually or disconnect old configurations.

Replacing it disconnects every tool using that account token. Download and import fresh configurations afterward. Existing named API tokens are unaffected.

If Flare can't load or replace the token, the error shows the server's reason when it gives one. For example, Too many requests means requests from your address replaced the token, or created or revoked invites, more than 60 times within a minute; wait a minute and try again. Otherwise the error reads Failed to fetch upload token or Failed to refresh upload token, which earlier versions showed for every failure.

Use named API tokens when a custom connection needs its own permissions, expiration, profile binding, or revocation. Downloading a standard screenshot-tool configuration does not create a separate named token for that tool.

Troubleshooting

Symptom	Check
Capture succeeds but upload fails	Test a browser upload; check the instance URL, token, quota, and file-size/type limits.
Tools stopped after replacing the token	Download and import new configurations or update the token in each script.
Link was created but clipboard is empty	Check ShareX/iTake's copy action, or install the clipboard utility required by the script and desktop session.
Correct credential, profile error	Confirm the selected profile still exists. A deleted profile or profile-bound token requires reconfiguration.
The generated URL uses an old host	Ask the administrator to correct the instance's public URL, then download the configuration again.
Upload succeeds but recipients cannot open it	Review visibility, password, and expiration. The copied link does not grant access to a private file.
Linux script exits with a missing-command error	Install the command it names. Scripts check for xsel, or for wl-copy when Wayland clipboard support was selected.
A script prints Upload failed: Network error or invalid URL	curl could not reach Flare. Check your connection, any TLS certificate error, and the address on the script's API_URL line.
A download fails with Invalid server URL configuration	The instance has no usable public address. Ask the administrator to set NEXTAUTH_URL to its public http or https origin, without a username, password, query, or fragment. Earlier builds answered Server configuration error when it was unset.
A download fails with Upload profile not found.	The profile was deleted, perhaps in another tab. Reload the page and pick another profile.