Lemora finished, but there is no new file: what to check
A completed action does not always produce another file. Some tools leave the source alone when it already meets the request or when there is nothing to change. Read the result message first, then check the save location. Repeating the same action without that check can leave you looking for an output the tool deliberately did not create.
Start with the result you need
- Read the message shown after the action. Distinguish an already-complete result from an error or a cancelled operation.
- Check beside the original, then Downloads/Lemora if folder access was not available.
- Match the message to the action: a size check, duplicate scan and compression pass have different success conditions.
- If the action failed, check the named file and reason before retrying. Keep the source while investigating.
This troubleshooting guide covers both file-writing tools and commands that return information without a new file.
Where to find these actions
- Tools → Resize: Small enough to email, under 1 MB, a percentage, or exact pixels. Asks for the size.
What you get
A clear explanation before another attempt
Already-small inputs, unchanged tables and unhelpful compression results can finish without a new file. Errors require separate investigation.
Works with: Supported local files selected in Finder.
An image is already under the size limit
Under 1 MB skips an input at or below 1,000,000 bytes. That is a size decision, not a format conversion. A small HEIC can therefore remain HEIC. If a form requires JPG, run JPG conversion separately, then check the converted file's size.
No duplicate rows were found
Remove Duplicates writes a cleaned copy only when it finds repeated whole rows under its comparison rules. A repeated customer ID with a different address is a different row and remains. Use the merged file when the result says no duplicates were found.
Compression could not make the file smaller
Compress keeps a useful smaller result rather than leaving a larger derivative. Text-heavy PDFs and already compressed media may have little room to shrink. A fixed upload limit may require another preparation step; it is not a reason to keep repeating the same pass.
Nothing was recognized or detected
Text extraction can report no text, Make Searchable can find no new text to add, and face redaction can report no detected faces. Read those outcomes narrowly. They describe what the action found, not proof that an image contains no words or a video contains no people.
The output exists in another folder
Results save next to originals when the app has the needed folder access, with Downloads/Lemora as the fallback. Check the result message and both locations before running the tool again. Actions such as Copy, Quick Look and Test do not create converted files in the first place.
Tested outcomes that do not create a new file
We reproduced two unchanged-input outcomes and one failure with generated files.
- The already-small HEIC completed with an already-under-1-MB message and no new file.
- The unique CSV completed with a no-duplicate-rows message and no new file.
- The silent video failed audio extraction; its output folder remained empty.
Tested 2026-11-15 with generated sample files in local debug build 1.0.0 (5) on macOS 27.0. This is not an App Store release test or a benchmark of arbitrary files.
Questions
Does no output mean the original was damaged?
No. The tools described here keep the source. Inspect the message to understand why no derivative was written.
Should I rerun the action immediately?
First check the outcome and save location. Rerunning cannot make a skipped small HEIC become JPG or turn different rows into whole-row duplicates.
Try this workflow on your Mac
Download Lemora on the Mac App Store Free to try: every feature for your first 25 actions. macOS 15 or later.