skip to content
PDF & file workflows practical workflow

Organise and Prepare a Working File Collection

Clean a Downloads, publishing, or image-output folder before archiving, sharing, or starting the next workflow.

real_life_scenario

A project folder contains source files, duplicates, drafts, generated outputs, and delivery copies. Nobody can confidently tell what should be kept or reused.

finished_outcome

A reviewed local folder structure with exact duplicates identified, intended files organised, and the last operation still reversible.

what_you_need

Prepare the inputs before opening the apps

  • A copied working folder rather than the only archive
  • A desired type- or date-based structure
  • Rules for exact duplicates
  • A plan for source, working, and delivery files

step_by_step

The working process

  1. 1

    Create a safe working copy

    Do not begin a large cleanup on the only copy of important work. Make or verify a backup and identify which folder is in scope.

  2. 2

    Scan before moving anything

    Use Batch File Organiser to inspect file types and exact duplicate results. Hash matches can reveal identical files even when names differ.

  3. 3

    Preview the proposed structure

    Choose type or date organisation and examine the complete plan. Look for project conventions that automated grouping should not override.

  4. 4

    Apply one understandable operation

    Run the approved organisation step locally. Verify representative folders immediately while the undo context is still clear.

  5. 5

    Separate masters from delivery copies

    Keep high-quality sources distinct from resized, compressed, watermarked, or enhanced outputs. This prevents accidental quality loss in later work.

  6. 6

    Prepare only the files that need it

    Use Batch Compress Image for lighter delivery or archive copies and Batch Enhance Image for selected print files. Neither action is a substitute for folder organisation.

human_checkpoint

Review before you call it finished

  • Is there a backup or safe working copy?
  • Were duplicate matches inspected before removal decisions?
  • Does the preview respect project-specific folders?
  • Are masters separated from derived outputs?

honest_boundaries

Limits and privacy

Practical limitation

Hash matching identifies exact duplicates, not the “best” edit. Organisation rules cannot infer every project convention, so preview and backup remain important.

Privacy boundary

Scanning, hashing, moving, compression, and enhancement run locally.

faq

Questions worth answering

Does duplicate detection decide which copy to delete?

It identifies exact matches. You still decide which path or copy belongs in the final structure.

continue_the_work

Related workflows

all use cases →
workflow://UC-29 6 steps

PDF & file workflows

Find Exact Duplicate Files by Hash

Identify byte-for-byte duplicate files on Windows even when their filenames differ, then review the matching paths before reorganising anything.

BFO
workflow://UC-15 5 steps

Social & image production

Compress Images to Save Storage Space

Create a lighter copy of an exported image collection for archiving, email, upload, or routine delivery.

BCI
workflow://UC-16 5 steps

Social & image production

Enhance Images for Printing

Upscale a selected image set against real print dimensions and inspect the result before ordering.

BEI