file organization

2 posts with the tag "file organization"

Blober Path Templates: Organize Files During Transfer

Jul 20, 2026

What Path Templating Means in Blober

A file transfer normally answers two questions: what should move, and where should it go. Blober adds a third: what destination path should each file receive?

That matters because copying a disorganized source without thinking about paths creates a disorganized backup. A bucket containing clip001.mp4, invoice.pdf, DSC_4821.ARW, and years of nested project folders can be copied exactly as it is, filtered to a useful subset, or rearranged into a new structure while it moves.

Blober path templates are destination rules. They combine ordinary folder text with variables such as {file_ext}, {file_created_date}, and {filename}. Blober evaluates the template separately for every matching file and creates that file's relative destination path.

media/{file_ext}/{file_created_date}/{filename}

For a video named GX015742.MP4 with a reported creation date of July 18, 2026, the relative result is:

media/mp4/2026-07-18/GX015742.MP4

If the selected destination folder is studio-archive, the complete destination becomes:

studio-archive/media/mp4/2026-07-18/GX015742.MP4

No separate organizer, database, script, or integration platform is involved. The organization happens as part of the copy or move.

Where the Feature Is in the App

Path setup spans three numbered sections in the workflow editor. For the step-by-step app reference, see the Workflows guide.

1. Source Configuration

Choose the source provider, authenticate it, then click Browse Files and Folders. You can select individual files, multiple files, folders, or an entire storage root when the provider supports it.

If at least one folder is selected, Advanced Filters (Optional) appears. It can restrict files by:

• File extension
• Created-date range
• File-size range
• Whether subdirectories are included
• Include glob pattern
• Exclude glob pattern

Source selection defines where Blober looks. Filters define which files inside that scope qualify.

2. Destination Configuration

Choose the destination provider and Select Destination Folder. Once the destination is complete, expand Advanced Path Template (Optional).

The Template Pattern field is appended beneath the destination folder. The variable list below the field can be clicked to add placeholders. Blober also shows an example output while the pattern is being edited.

3. Preview & Summary

The preview shows active filters, the destination template, source items, and expected destination paths. This is where a path rule becomes understandable before files move.

Do not treat preview as decoration. A template can deliberately flatten a hierarchy, split files into new folders, or rename every destination. Preview is the check that the rule means what you think it means.

The Three Path Modes

Mode 1: Copy the Structure As-Is

Leave Advanced Path Template empty and keep Include Subdirectories enabled. Blober automatically retains the relative directory structure beneath the selected folder.

Selected folder:

Projects/
  Client-A/
    Final/
      film.mp4

Destination result:

Client-A/Final/film.mp4

This is the right mode for a faithful backup. You do not need a template merely because templates exist.

Mode 2: Flatten the Selection

Leave the template empty and disable Include Subdirectories. Files are placed by filename without their relative source folders.

This can be useful when collecting documents into one destination, but duplicate filenames from different source folders may target the same destination name. Preview the result carefully.

Mode 3: Build a Custom Path

Enter a path template. The template takes control of the relative destination path. Automatic subdirectory preservation no longer adds the source hierarchy behind the scenes.

That rule is easy to miss:

{file_created_date}/{filename}

organizes by date but does not preserve source subfolders.

To retain relative source folders inside a custom path, explicitly include {file_dir}:

{file_created_date}/{file_dir}/{filename}

Read the dedicated {file_dir} guide before relying on it. Its value depends on whether a file or folder was selected and how deeply the file sits beneath that selected folder.

Every Available Variable

Variable	Meaning	Example
{current_date}	Current processing date	2026-07-20
{current_datetime}	Current processing date and time	2026-07-20_14-30-00
{file_created_date}	Source-reported creation date	2026-07-18
{file_created_datetime}	Source-reported creation date and time	2026-07-18_09-15-30
{file_modified_date}	Source-reported modification date	2026-07-19
{file_modified_datetime}	Source-reported modification date and time	2026-07-19_16-45-22
{file_accessed_date}	Source-reported access date	2026-07-20
{file_accessed_datetime}	Source-reported access date and time	2026-07-20_12-00-15
{filename}	Complete filename	GX015742.MP4
{filename_no_ext}	Filename without extension	GX015742
{file_ext}	Extension without the dot	mp4
{file_size}	Exact size in bytes	1572864
{file_size_mb}	Exact size in MB, rounded to two decimals	1.50
{file_dir}	Relative directory beneath the selected folder	Day-2/Camera-A

These are deterministic metadata substitutions, not AI classifications. Blober does not inspect an image and infer a client, location, or subject. If Client-A is not present in a selected path, filename, or available variable, a template cannot invent it.

How Template Evaluation Works

Suppose the destination folder is:

Archive

The selected source folder is:

Shoots

and one matching file is:

Shoots/Wedding-2026/Camera-A/DSC_4821.ARW

For that file:

{file_dir} = Wedding-2026/Camera-A
{filename} = DSC_4821.ARW
{filename_no_ext} = DSC_4821
{file_ext} = arw

This template:

originals/{file_dir}/{filename}

produces:

Archive/originals/Wedding-2026/Camera-A/DSC_4821.ARW

This template:

by-type/{file_ext}/{filename}

produces:

Archive/by-type/arw/DSC_4821.ARW

The second rule intentionally discards the source folder hierarchy because it does not contain {file_dir}.

Variables and Filters Solve Different Problems

Filters decide whether a file participates. Variables decide where a participating file lands.

For example:

Include pattern: **/*.{jpg,png}
Exclude pattern: **/thumbnails/**
Template: images/{file_created_date}/{filename}

The include pattern rejects non-image extensions. The exclude pattern removes thumbnails. The path template organizes the remaining files by creation date.

Keeping those concepts separate makes workflows easier to reason about:

1. Select a source boundary.
2. Filter the files inside it.
3. Build the destination path for each match.
4. Preview.
5. Copy or move.

Important Metadata Limits

Path templates use metadata supplied by the source provider or filesystem. Not every backend describes dates and sizes in exactly the same way.

• A cloud object may expose upload or modification time rather than the camera's original capture time.
• Access time may be unavailable or unhelpful on object storage.
• Unknown file size becomes NO_SIZE or NO_SIZE_MB when used in a template.
• {file_size_mb} creates an exact numeric folder such as 142.53; it does not automatically create human categories such as small or large.
• File extensions come from filenames. A misleading extension is not content inspection.

These limits do not make templates unreliable. They define what the rule can truthfully know. Use preview to inspect real metadata from the selected source.

Copy and Move

Use Copy when:

• Creating a backup
• Testing a new destination structure
• Building a second organized library
• Keeping the source as the working location

Use Move when:

• The destination has been verified
• The source should be cleaned up
• Files are being retired from expensive active storage

A move deletes the source after successful transfer. For any new path rule, run a representative copy first.

Blober can also reorganize between supported locations on the same provider, but source and destination cannot overlap. Do not place a destination inside the selected source tree. Choose a separate folder, bucket, container, or account.

Detailed Guides in This Series

• How {file_dir} Really Works
• File Selection and Glob Include/Exclude Filters
• Organize Files by Created, Modified, Accessed, or Current Date
• Organize Files by Type and Extension
• Filter and Organize Files by Size
• Organize Blob Storage Without Advanced Search
• Media and Professional File-Organization Workflows
• Copy As-Is, Organize During Backup, or Reorganize With Move

A Safe First Workflow

1. Create a new workflow and choose Copy.
2. Select one folder containing several levels, file types, and sizes.
3. Choose a separate destination folder.
4. Enter {file_ext}/{file_dir}/{filename}.
5. Inspect every example in Preview & Summary.
6. Save and run the workflow.
7. Verify the actual destination before scaling up.

That small test reveals exactly how the source provider reports dates, extensions, sizes, and relative folders. Once the output is correct, the same saved workflow can handle a much larger selection.

Download Blober at blober.io to organize files as they move between cloud storage, object storage, local disks, and network drives.

Tags:

• blober
• path templates
• file organization
• cloud storage
• object storage
• file transfer
• backup

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:

1. "I need another copy exactly as this is."
2. "I need a backup, but only of useful files."
3. "I need a second copy arranged more clearly."
4. "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:

1. Build the intended workflow as Copy.
2. Test a representative folder.
3. Verify destination paths and open sample files.
4. Confirm counts and task results.
5. 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.

Tags:

• blober
• copy files
• move files
• backup workflow
• file organization