Batch erase

Erasing is a hand operation: somebody paints, looks and paints again. A folder cannot be painted, and a batch that applied one painted region blindly to a hundred different frames would erase a piece of most of them. What a folder can have is a rule — the same orange imprint in the same corner of every scan from one roll, the same badge an app burned in at the same inset, the same dust on every frame from one scanner.

Each rule is solved per file and allowed to refuse. A rectangle measured on one frame size is never stretched onto another; a picture with no imprint gets nothing written; a dust proposal covering more than the share you set is held for review, because that much is texture, not dust. Every finished row reports what was covered, how far the pixels inside and outside moved in the file actually written, and how busy the surroundings were — the one honest hint about whether a fill is likely to be right.

1. 1Drop the folder. Select or drop several pictures. Nothing is read until you press the button.
2. 2Choose the rule. Film date imprint, carried rectangle, phone timestamp, dust and scratches, or a corner box with its size and inset.
3. 3Choose the fill and format. Chosen per picture, edge march or patch search; PNG to keep every other pixel exactly.
4. 4Run it. Rows fill in one by one: done, nothing found, refused (with why), or unreadable. A failure never stops the run.
5. 5Download the ZIP. Named pictureeraser-batch with the date. Check the rows marked busy at 1:1 first.

• Only marks in a predictable place, or that the rules can detect, can be batched. Objects, people and anything that needs judgement are one picture at a time.
• The structure-aware model is not offered over a folder.
• Rules are heuristics: the imprint and timestamp searches miss some stamps and say so; the dust rule cannot tell dust from stars.
• Large folders take a while; files run one at a time to keep memory steady.