ShareX Annotations Not Saving: How to Fix Lost Edits

You capture an image in ShareX, add an arrow, box, text label, blur, or highlight, and everything looks correct in the image editor. But when you open the saved file, paste the image, or check the uploaded link, the annotations are missing. In most cases, this does not mean the editor failed. It means the original screenshot and the edited output followed different save, clipboard, or upload paths.

The most likely causes are closing the editor without committing the result, running after-capture tasks before editing is complete, uploading the original file instead of the edited image, copying one version while saving another, overwriting an unexpected destination, or editing a temporary copy. The steps below isolate those possibilities without requiring advanced Windows knowledge.

1. Confirm the Symptom and Reproduce It With a Simple Test

Before changing settings, determine exactly where the annotations disappear. A saved file, clipboard image, and uploaded image are separate outputs. One can contain your edits while another still contains the original capture.

1.1 Create a controlled arrow test

Use a large, obvious annotation so there is no uncertainty about which version you are viewing.

1. Capture a small, recognizable area of the screen.
2. Open the capture in the ShareX image editor.
3. Add one large red arrow across the middle.
4. Save or complete the editor action rather than simply closing the window.
5. Open the resulting file directly from its saved location.
6. Paste the clipboard into Paint or another blank image editor.
7. If an upload task ran, open the uploaded result separately.

Record which outputs contain the red arrow. This quickly divides the problem into three categories: the edited file was never created, the edited file exists but the clipboard contains another version, or the upload used the original capture.

If all three outputs show the arrow, the basic editor workflow is working. Stop changing global settings and investigate the specific hotkey, workflow, or destination that previously produced the wrong result.

1.2 Verify that you are opening the latest file

Duplicate names, multiple screenshot folders, and cached previews can make a correct save look unsuccessful. In File Explorer, switch to Details view and inspect the file name, folder path, size, and modified time. Open the file from that exact location instead of using a recent-files shortcut.

If the modified time matches your test and the arrow appears, saving is working. The earlier symptom probably involved an old file, a second destination, or a different stage of the workflow.

2. Check the ShareX Settings Directly Related to This Problem

ShareX can chain several actions after a capture, including opening the image editor, copying an image, saving a file, and uploading it. The order and selection of these tasks determine whether later actions receive the original capture or the edited result.

2.1 Save from the editor instead of closing it

Closing an editor window is not always equivalent to accepting and saving the edited output. If you add annotations and then dismiss the window with its close button, cancel an operation, or decline a save prompt, the original screenshot may remain unchanged.

Repeat the arrow test and use the editor command that explicitly saves, accepts, or completes the image. Read any confirmation prompt carefully. If ShareX asks whether to save changes, choose the option that preserves them.

Success means that the file opened from File Explorer contains the arrow immediately after the editor finishes. Once that happens consistently, do not keep changing editor settings.

2.2 Review after-capture tasks and their order

Open the ShareX after-capture task configuration used by the affected hotkey or workflow. Look specifically for tasks related to opening the image editor, saving the image to a file, copying the image to the clipboard, and uploading the image.

If save, copy, or upload actions complete before editing, those actions can operate on the unannotated capture. The editor may then display a separate working image, creating the impression that the visible edits should automatically replace every earlier output.

For troubleshooting, simplify the workflow so editing occurs before the final save, clipboard, or upload action. Avoid enabling several destinations at once until the arrow test succeeds.

Success means the next action in the chain receives the image containing the arrow. For example, if uploading is the goal, open the uploaded image and verify that the arrow is present. If it is, stop rearranging tasks.

2.3 Check image editor workflow settings

ShareX supports different ways to reach the image editor. You might edit immediately after capture, open an existing image later, or launch the editor through another tool or task. These paths do not necessarily use the same source file or subsequent actions.

Confirm that the affected hotkey actually enables the editor as part of its after-capture workflow. Also check whether the editor is expected to return its result to the task chain or merely open an image for manual editing. If you maintain multiple hotkeys, compare the failing hotkey with one that works.

Success means the same hotkey reliably opens the editor and produces an edited output through the intended save, copy, or upload path.

2.4 Separate copy to clipboard from save to file

Copying and saving are independent operations. Saving an annotated file does not prove that the clipboard was refreshed with that file. Likewise, pasting an annotated image does not prove that the file on disk was updated.

Test each destination independently:

• For the file test, save the edited image and open it directly in File Explorer.
• For the clipboard test, copy the completed image and immediately paste it into a blank Paint document.
• For the upload test, inspect the final remote image rather than relying only on a thumbnail or notification.

If only the clipboard is wrong, focus on when the copy action runs. If only the saved file is wrong, focus on the editor save command, path, and overwrite behavior. If only the upload is wrong, focus on which local image the upload task receives.

3. Check Windows, Destination, and Workflow Factors

Once the task sequence is sensible, check whether Windows or the selected destination is causing you to inspect a different file from the one ShareX edited.

3.1 Check file overwrite behavior

If you edit an existing screenshot, ShareX or the editor may save to a new name rather than overwrite the original. The opposite can also happen: an automated action may replace a file after you inspected it. File-name templates that generate similar names make this especially easy to miss.

During testing, choose a new, unmistakable file name such as sharex-arrow-test.png and save it to a simple folder you can access. Do not reuse the original name. Open that exact file and check its modified time.

Success means the newly named file contains the annotation and has the expected current modified time. If so, the editor works and the issue is file selection or overwrite behavior, not annotation rendering.

3.2 Avoid editing a temporary copy accidentally

An image opened from task history, a preview, a temporary location, or another application may not be the same file that your automation later uploads. You can successfully annotate a temporary copy while the original screenshot remains untouched in its normal destination.

To avoid this, identify the full source path before editing. Then use Save As to create a clearly named edited file in a known folder. If an upload is required, upload that explicit file during the test rather than depending on an earlier automated task.

Success means the source and destination paths are unambiguous, and the uploaded image matches the named edited file.

3.3 Check folder permissions and protected locations

If the editor appears to save but the file does not change, test a normal user-writable folder such as Pictures or a new folder inside Documents. Avoid system folders, application installation directories, network locations, and tightly controlled synchronized folders during diagnosis.

Also pay attention to save errors, access-denied messages, read-only files, or prompts asking for another location. Security software or controlled folder policies can affect writes, but do not disable security features as a first step. A successful save to a standard local folder is enough to show that the annotation workflow itself is functional.

3.4 Distinguish a bad upload from a stale preview

An upload destination, browser, messaging application, or content delivery cache may continue showing an older image, particularly when a file is replaced under the same name. Open the final URL in a private browser window or download the remote file and inspect it locally. If possible, use a unique file name for the test upload.

If the downloaded remote image includes the red arrow, the upload succeeded and the earlier view was stale. If the local edited file has the arrow but the remote download does not, the upload step selected the wrong source or occurred before editing.

4. Run a Clean Temporary Test With Minimal ShareX Settings

A minimal test removes automation from the equation. It is safer and faster than changing many unrelated settings at once.

1. Temporarily disable upload actions for the test workflow.
2. Temporarily disable unrelated actions such as OCR, effects, printing, or extra clipboard operations.
3. Keep only the capture and image editor steps active.
4. Capture a small region and add one large red arrow.
5. Use Save As and choose a unique PNG file in a known local folder.
6. Open the PNG directly from File Explorer.

If the arrow is present, ShareX can render and save annotations correctly. Re-enable one required action at a time. Add clipboard copying, retest, then add uploading and retest. The first action that causes the wrong version to appear identifies the problematic stage.

If the minimal save still lacks the arrow, repeat the test while paying close attention to the editor completion command and any prompts. Also try a new output name to exclude overwrite confusion. There is no value in adjusting network, upload, or clipboard settings until a direct local Save As test works.

5. Check Task History, Logs, and Recent Workflow Output

Task history can help identify which file ShareX saved or uploaded. Open the most recent task and compare its time, file path, thumbnail, and URL with the controlled test. Do not assume that the top visible file in a folder or an old notification belongs to the latest capture.

5.1 Compare task time with file modified time

Match the task timestamp to the modified time shown in File Explorer. A mismatch suggests that you opened an earlier file or that a later operation created another output. File size can provide another clue because annotations often change the encoded image size, although size alone is not proof.

Success means the task, local path, and modified time all identify the same annotated image.

5.2 Look for useful errors rather than unrelated warnings

If ShareX reports an error, focus on messages involving saving, access, file paths, clipboard operations, or uploads. A network failure cannot explain why a manually saved local PNG lacks annotations, while a path or permission error can.

When reviewing logs, note the exact time of the arrow test and inspect entries around that time. This prevents older, unrelated failures from distracting the diagnosis. If you seek support, include the steps used, the intended output, the actual output, and any relevant error text. Remove private URLs, tokens, or sensitive file paths before sharing logs.

6. Quick Fix Checklist

• Add a large arrow and complete the editor action instead of closing or cancelling.
• Save to a new, clearly named file in a normal local folder.
• Open the exact saved file and verify its modified time.
• Confirm editing happens before save, clipboard, and upload tasks.
• Test clipboard output separately by pasting immediately into Paint.
• Check that the upload uses the edited image rather than the original capture.
• Avoid editing a temporary preview or a task-history copy unintentionally.
• Use a unique upload name to rule out cached remote images.
• Reduce the workflow to capture, edit, and Save As.
• Re-enable automation one action at a time and stop when all required outputs match.

The most reliable stopping point is simple: the locally saved file, clipboard paste, and uploaded result that you actually need all contain the test arrow. Once that is true, avoid additional setting changes because they can reintroduce ambiguity.

7. Frequently Asked Questions

7.1 Why do annotations appear in the editor but not in the saved screenshot?

The editor may be showing a working copy while the saved file is still the original capture. This commonly occurs when the editor is closed without committing changes, when the save task runs before editing, or when the edited result is written under another name. Use Save As with a unique name and open that exact file to determine which cause applies.

7.2 Why does the saved file include annotations but the clipboard does not?

The clipboard was probably populated before editing or was not refreshed after the edited image was saved. Copying and saving are separate actions. Paste into Paint immediately after completing the editor, and adjust the workflow so the final edited image is copied only after editing.

7.3 Why does ShareX upload the image without my arrows or blur?

The upload may occur before the image editor returns the edited output, or it may reference the original file path. First confirm that a local, uniquely named file contains the edits. Then upload that exact file manually. If the manual upload is correct, revise the automated task order so upload receives the edited version.

7.4 Can I overwrite the original screenshot safely?

You can overwrite it when the destination permits writing and you are certain that the editor is targeting the correct file. During troubleshooting, however, Save As is safer because it prevents confusion between original, temporary, and edited copies. After the workflow is verified, you can choose an overwrite approach that fits your needs.

7.5 Does reinstalling ShareX usually fix lost annotations?

Not when the root cause is task order, destination selection, clipboard timing, or closing the editor without saving. A controlled local arrow test is more informative than reinstalling. Consider repair or reinstallation only after a minimal Save As test fails and you have ruled out permissions, file selection, and editor completion behavior.

7.6 What information should I collect if ShareX is still not working?

Record the hotkey or capture method, enabled after-capture tasks, exact editor completion action, output folder, file modified time, and whether the local file, clipboard paste, and upload contain the annotation. Include relevant error text and the time of the test. This evidence makes ShareX troubleshooting much faster than a general report that edits disappeared.