Organize files
on Windows.

Start with a mixed personal folder

Use a personal inbox or Downloads folder rather than a whole drive, installed application or development project. Choose a destination outside the source tree and keep an independent copy of important originals.

Write down the outcome you want: photos grouped by month, documents separated from installers, or a reviewed set of files copied to an archive. Avoid sorting a project’s assets away from the document that links to them.

Choose the rule before the destination

Type-based rules use file categories; they do not understand the business meaning of every document. Date-based organization also needs a named date field. A file’s modification time is not necessarily the date a photograph was taken or an invoice was issued.

Use explicit document keyword rules only when the actual text supports them. A filename can be misleading, OCR can miss words, and an ambiguous document should remain for review. Keep sensitive documents out of an assistant workflow unless you intend to share the requested text with its client.

Decide what happens at collisions

Two files named report.pdf are not necessarily the same report. Review the entire proposed destination path. If occupied targets are retained or keep-both numbering is offered, inspect those names instead of accepting an ambiguous overwrite.

A copy produces a second instance and needs destination space. A move can break links from another application. Neither successful organization nor matching contents automatically authorizes removal of a source.

Preview in WhimRoom

1. Choose the organization task and personal source folder. Select supported rules and a separate destination.
2. Read the plan. Inspect proposed names, destinations, conflicts and exclusions. Check several documents against the intended rule.
3. Approve a small batch. Use the native review for the interactive operation. Do not start by enabling an unattended policy.
4. Open the outputs. Check expected file counts, names, contents and the recorded result before expanding the scope.

Make automation a separate decision

A saved automatic policy may run according to its configured conditions without a fresh review for each item. Agree the source, destination, rules and conflict behavior first. Test it with disposable fixtures and confirm how to stop it and inspect its activity.

If the real task is combining two existing trees, use missing-only folder combination. For copies to another drive, follow copy verification.