Rules

Build predictable file rules and understand ordering, conditions, actions, and conflict behavior.

A rule answers three questions: which files match, what should happen, and whether later rules may continue.

Read the summary first

Collapsed rule cards show a natural-language summary of the main conditions, action, and match policy. Use it as a quick check, then expand the rule when you need to edit details.

Conditions

Rules can inspect attributes such as extension, name, category, size, created or modified date, tags, source app, folder path, duplicate status, and indexed content. Add conditions for a narrower match, group alternatives together, or negate a condition when a file must not match it.

Keep the first rule simple. Deep condition groups are useful, but they are harder to audit at a glance.

Actions

A rule can move, copy, rename, archive, compress, tag, send to Trash, or run supported automations. Multiple action steps run in the order shown. Check every action value—especially destination folders and rename templates—before execution.

Stop or continue

• Stop after match: after this rule handles a file, lower rules do not process it.
• Continue matching later rules: later rules may also add actions. This is useful for tags and review workflows.

Put narrow, high-priority rules above broad catch-all rules. For example, an invoice rule should precede a general PDF rule.

Rule Health Check

Run the health check after editing or reordering rules. It reads rules and the current scan cache without changing files. It can flag missing values, invalid regular expressions, empty groups, incomplete actions, rules intercepted by a higher stop rule, and risky background behavior.

An estimated match count depends on the latest scan. Scan enabled folders first when the report lacks enough data.