move files

Copy, Organize, or Move Files With Blober

Jul 20, 2026

One Feature, Four Different Intentions

The same file browser and destination controls can serve very different goals. Problems occur when the action does not match the intention.

Before choosing filters or a path template, decide which statement is true:

"I need another copy exactly as this is."
"I need a backup, but only of useful files."
"I need a second copy arranged more clearly."
"I need the files relocated and removed from the source."

Blober supports all four, but the safest settings differ.

1. Faithful Copy As-Is

Use this for disaster recovery, provider migration, or preservation when changing paths would make verification harder.

Action: Copy
Source: selected files or folders
Advanced Filters: unchanged
Include Subdirectories: enabled
Path Template: empty

Blober preserves the relative folder structure under the selected source folder. This is the simplest workflow and often the correct one.

Do not add a path template just to appear organized. A backup's first job may be fidelity.

2. Filtered Backup

Use this when the source contains rebuildable or irrelevant material:

Action: Copy
Selection: broad project folder
Include: required extensions or paths
Exclude: proxies, caches, temp files, dependencies
Path Template: empty or {file_dir}/{filename}

The destination can preserve the original hierarchy while omitting noise.

This approach is useful for:

Source code without installed dependencies
Video originals without proxies
Business records without autosaves
Approved exports without drafts

An exclusion rule is a recovery-policy decision. Confirm that omitted files can truly be rebuilt or discarded.

3. Organize While Backing Up

Use this when the source should remain untouched but the new copy should be easier to browse.

Action: Copy
Template: {file_ext}/{file_created_date}/{file_dir}/{filename}

This can split a mixed source by type and date while preserving nested project context.

It is especially valuable when copying from:

Flat object-storage prefixes
Camera-cloud libraries
Shared drives with inconsistent top-level folders
Old disks accumulated over many years

The organized destination is a second interpretation of the source, not proof that the original can be deleted.

4. Reorganize With Move

Use Move only when the files should disappear from the source after successful transfer.

Appropriate examples:

Retiring completed projects from expensive active storage
Moving approved files out of an intake area
Relocating files into a final archive after verification
Cleaning up a provider after a completed migration

Move combines transfer and deletion. A wrong include rule may leave files behind; a wrong path rule may place them somewhere unexpected; a broad selection may relocate more than intended.

The safe sequence is:

Build the intended workflow as Copy.
Test a representative folder.
Verify destination paths and open sample files.
Confirm counts and task results.
Use Move only for the verified scope.

Organizing Into Another Folder on the Same Provider

Blober can use the same supported provider on both sides when the adapter and action allow it. This is useful for reorganizing one bucket, container, drive, or account into another location.

The destination must not be:

The same folder as the source
Inside a selected source folder

An overlapping destination could be picked up again while Blober scans the source, or cause a file to be copied onto itself, so Blober blocks it.

Choose:

A sibling folder
A different bucket or container
A separate account
Another provider

Example:

Source: incoming-media
Destination: organized-media
Action: Copy
Template: {file_ext}/{file_created_date}/{file_dir}/{filename}

What Saved Workflows Add

A workflow records the source, selection, filters, destination, action, and path expression. That makes a proven organization rule repeatable.

Examples:

Run the same camera ingest after each shoot.
Copy each month's reports into a dated archive.
Move completed exports from intake to delivery.
Archive large files after projects close.

Repeatability is valuable only when the rule remains appropriate. Preview changes in source data before assuming an old filter still represents current folders and naming conventions.

Preview Before Saving and Running

Preview & Summary answers:

Which filters are active?
Which files currently match?
How many items and known bytes are represented?
What destination path will each example receive?
Is {file_dir} preserving the expected relative structure?

The workflow is saved before it is run. Saving the configuration does not itself transfer files. Running it creates a task that tracks per-file progress and results.

Choosing the Minimum Necessary Workflow

Goal	Action	Filters	Template
Exact second copy	Copy	None	Empty
Exclude noise	Copy	Yes	Usually empty
Create organized library	Copy	Optional	Yes
Relocate verified files	Move	Optional	Optional

Start at the leftmost simple solution that meets the actual need. Filters and templates are powerful because they are optional.

Read the complete path-template guide for path behavior, or explore professional workflow examples.