Organize Cloud Files by Created, Modified, or Backup Date

Organize cloud files by created modified accessed or backup date with Blober

Jul 20, 2026

Why Date Organization Solves Real Retrieval Problems

Dates are one of the few metadata fields shared by photos, videos, documents, exports, and cloud objects. When filenames are meaningless and folders are inconsistent, a date-based destination gives users a predictable place to start.

Examples:

A photographer needs all files created during a shoot.
An agency needs exports modified during the current campaign.
A business needs monthly snapshots of reports.
An IT team needs each backup run separated from previous runs.
A creator needs footage grouped by the date supplied by the source.

Blober supports two different date operations: filtering which files qualify and placing qualified files into date-based paths.

Where Date Controls Live

After selecting a source folder, expand Advanced Filters (Optional) in Source Configuration. Created Date Range can restrict the source to any time, the last 24 hours, 7 days, 30 days, or 90 days.

After selecting the destination folder, expand Advanced Path Template (Optional). Date variables can then appear anywhere in the destination path.

The source date filter currently evaluates file creation time. Choosing a path variable is independent: matching files can be arranged by created, modified, accessed, or current processing date.

The Four Date Concepts

Current date

Use:

{current_date}
{current_datetime}

These represent when Blober processes the file. They answer, "When did this workflow place the file here?"

backup-runs/{current_date}/{file_dir}/{filename}

This is useful for snapshots and migration batches. It is not the file's historical creation date.

File creation date

Use:

{file_created_date}
{file_created_datetime}

These use creation metadata reported by the source adapter.

created/{file_created_date}/{filename}

This is often suitable for camera media and newly produced documents, but cloud providers may interpret "created" as the time an object entered that service rather than the original camera capture time.

File modification date

Use:

{file_modified_date}
{file_modified_datetime}

Modification time is useful for edited deliverables, reports, design exports, and files whose important event is the last save rather than initial creation.

last-edited/{file_modified_date}/{file_dir}/{filename}

File access date

Use:

{file_accessed_date}
{file_accessed_datetime}

Access time can be useful on filesystems that maintain it accurately. It is often weaker for object storage, where an access timestamp may not be exposed, may not mean "last viewed," or may be mapped from other provider metadata.

Do not choose access date merely because it exists in the variable list. Preview real values from the intended source first.

Date Versus Datetime

The date form creates broader groups:

2026-07-20

The datetime form includes hours, minutes, and seconds:

2026-07-20_14-30-00

Use a date for browsable daily folders. Use a datetime when separating runs, reducing filename collisions, or preserving event ordering matters.

For example:

exports/{file_modified_date}/{filename}

creates one folder per modification day, while:

exports/{file_modified_datetime}_{filename}

adds the timestamp to each filename.

Preserve Source Context

A date-only template can merge files from unrelated source folders:

{file_created_date}/{filename}

To keep project or camera subfolders beneath the selected source boundary:

{file_created_date}/{file_dir}/{filename}

Remember that {file_dir} is empty for directly selected files and files at a selected folder's root. Read how file_dir is calculated before using it as the only project identifier.

Real Scenarios

Wedding photographer

Select the whole wedding folder, include RAW and video extensions, and use:

originals/{file_created_date}/{file_dir}/{filename}

This groups media by source-reported creation day while retaining nested camera folders.

Monthly business archive

Select the reports folder and use:

report-archive/{current_date}/{file_dir}/{filename}

Each workflow run enters a dated snapshot folder. Use Copy so the working reports remain untouched.

Finished design exports

Select campaign folders, include PDF/SVG/PNG/WebP, exclude draft folders, and use:

deliverables/{file_modified_date}/{file_dir}/{filename}

The destination reflects when deliverables were last changed.

Incident or compliance export

When an export must be tied to the exact transfer:

exported/{current_datetime}/{file_dir}/{filename}

The workflow time is explicit even if source dates are inconsistent.

What Blober Can and Cannot Know From a Date

Blober organizes from the metadata each source provides. It does not read EXIF capture dates from inside an image or work out a date from what the photo shows.

Before a large transfer:

Select a representative folder.
Enter the intended date template.
Review several source and destination examples.
Check files from different providers or upload histories.
Use Copy for the first run.

If the source reports upload time as creation time, the preview will reveal it. Choose modified date, current date, or a simpler preserved hierarchy based on the actual data rather than the variable's name alone.

See the complete path-template guide for every variable and the copy-versus-move guide for a safe rollout.