Safety & how it works

Is it safe? Can it damage my files?

• A conversion only runs when you press a button. Dropping items just lists them.
• File contents are never touched — only the name is rewritten, via POSIX rename(2).
• If a file with the target name already exists, it is never overwritten — the filesystem is asked to rename only if the name is free, and a clash just marks that row as failed.
• It runs inside the App Sandbox; it only sees what you explicitly hand it.
• Every conversion is reversible — compose then decompose (or the reverse) returns the exact original bytes.
• Unreadable items never vanish silently — a warning below the list shows how many, and why.
• “Remove” in the UI only drops the row from the list. JamoMoa has no code path that deletes from disk.

The edge cases are covered too

• Symbolic links — judged and renamed by the link’s own name, not its target’s. The target file is never touched.
• App bundles (.app) — .app bundles found inside a folder are never descended into (so a bundle can’t break). Drop an .app directly and only its own name is listed.
• Network and external volumes — folders on SMB / NFS volumes scan recursively and convert the same way.

Can it handle a lot of files at once?

Yes. The list stays smooth at tens of thousands of entries, and Compose All / Decompose All show a live progress count (e.g. Working… (500/50000)) so you can see how far along a big batch is.