File Organization Workflows for Creators, SMEs, and IT

Most people already have the tools they work in. What they need is for files to move between those tools and land in a usable structure, without importing and tagging everything in yet another platform.

Blober works at that boundary. A source can be local storage, network storage, a cloud drive, a camera cloud or object storage, and a destination can serve editing, collaboration, delivery or archive. Selection, filters and path templates decide what crosses and how it lands.

Treat the examples below as starting points to adapt. Each one gives the problem, the source scope, the filters, the path and a safe action.

A shoot folder contains RAW files, JPEG previews, edited TIFFs, contracts and exports. Sending or archiving the whole folder wastes storage and exposes internal work.

For the RAW archive:

Selection: the shoot folder
File Types: CR2, NEF, ARW, DNG, RAW
Action: Copy
Destination: object storage
Template: originals/{file_created_date}/{file_dir}/{filename}

For client delivery:

Selection: the same shoot folder
Include: **/*.{jpg,jpeg,png,tif,tiff}
Exclude: **/{preview,previews,draft,drafts}/**
Action: Copy
Destination: client cloud folder
Template: delivery/{file_dir}/{filename}

Both workflows read the same shoot folder, and the working library stays where it is.

Original camera media, proxies, render caches, review files and masters are mixed across nested project folders. Proxy media may be large, but it can be replaced.

Selection: all completed project folders
Include: **/*.{mp4,mov,mxf,braw,r3d}
Exclude: **/{proxy,proxies,cache,temp,render-cache}/**
Size: Large
Action: Copy
Template: masters/{file_created_date}/{file_dir}/{filename}

The glob exclusion does more than the size filter, because a large proxy is still a proxy. Path conventions, type and size together give a better set of candidates.

GoPro footage is in GoPro Cloud, finished edits are in Google Drive, thumbnails are in Dropbox, and old projects are on a NAS.

Create one workflow per source and point them all at one archive:

GoPro destination path: gopro/{file_created_date}/{filename}
Edited-video path: edited/{file_modified_date}/{file_dir}/{filename}
Thumbnail path: thumbnails/{file_modified_date}/{filename}
NAS project path: projects/{file_dir}/{filename}

The services never have to connect to each other. Blober connects to each one, and the shared destination layout keeps the archive consistent.

Editable design sources and exported assets sit beside drafts, autosaves and review versions. Developers or clients need only the approved SVG, PNG, PDF and WebP files.

Selection: approved campaign or client folders
Include: **/*.{svg,png,pdf,webp}
Exclude: **/{draft,drafts,review,autosave}/**
Action: Copy
Template: assets/{file_ext}/{file_dir}/{filename}

Where you can, let the folder selection carry the approval. Selecting a known Approved folder is safer than inferring approval from every possible filename.

Every client uses a different destination: Dropbox, Google Drive, object storage or a local drive. Internal project folders should not be handed over wholesale.

Build a reusable handoff workflow:

• Select final and legal-release folders.
• Include deliverable media and documents.
• Exclude internal notes, proxies, and drafts.
• Copy to the client's destination.
• Use Client-Delivery/{file_dir}/{filename}.

For each client you change the credentials and destination, and the agency's selection rules stay the same.

A shared drive mixes current records, old invoices, scans, spreadsheets and temporary office files. Staff need the shared drive left as it is, and the business needs a second durable copy.

Selection: Finance, Contracts, Reports
Include: **/*.{pdf,doc,docx,xls,xlsx,csv}
Exclude: **/{temp,autosave,draft,drafts}/**
Action: Copy
Template: business-records/{file_ext}/{file_modified_date}/{file_dir}/{filename}

The type and date folders make the archive easier to browse later, and {file_dir} keeps each department's folders beneath its selected folder.

One study tree contains large datasets, notebooks, papers, charts and documentation. Collaboration storage is convenient for papers but expensive or awkward for multi-terabyte data.

Use two workflows:

1. A large dataset archive: size Large, the relevant binary and data extensions, and object storage as the destination.
2. Research documentation: PDF, Markdown, notebooks and CSV summaries, with a collaboration drive as the destination.

Preserve {file_dir} so the experiment and study structure survives both transfers.

Application trees contain source, configuration, uploaded assets, dependencies, caches, builds and logs. Copying everything adds cost and clutters a recovery.

Selection: application and service folders
Include: **/*
Exclude: **/{node_modules,cache,tmp,temp,dist,build,coverage}/**
Action: Copy
Template: systems/{file_dir}/{filename}

Match the exclusions to your recovery plan. A folder whose name sounds generated still belongs in the backup if the organization cannot rebuild it.

A single huge migration is hard to estimate, validate and retry, and different data classes have different owners and destinations.

Create separate workflows by:

• Department or selected prefix
• File type
• Size class
• Date window
• Include/exclude convention

Each workflow then has a smaller preview, a clear owner, and a destination path that fits its data class. That is often easier to audit than one huge transfer rule.

Family photos and videos are spread across disks and clouds with inconsistent folders.

Selection: camera uploads and old media folders
Include: **/*.{jpg,jpeg,heic,png,mp4,mov}
Action: Copy
Template: personal-media/{file_created_date}/{file_dir}/{filename}

Check the creation dates in the preview first. A cloud provider may report the upload time, not the original capture time. If the dates are wrong, organize by {file_dir} and filenames instead of building a timeline that misleads.

1. Select the smallest meaningful scope.
2. Use Copy first.
3. Combine only filters that express a real rule.
4. Preserve {file_dir} when project hierarchy matters.
5. Inspect Preview & Summary.
6. Verify actual destination files.
7. Scale or move only after the result is trusted.

How do I separate RAW originals from JPEG deliverables? Run two Copy workflows on the same shoot folder. One filters to RAW extensions and sends them to an archive; the other includes JPEG, PNG and TIFF files and sends them to the client's folder.

Can I leave proxy files out of a video backup? Yes. Exclude the proxy and cache folders with a glob such as **/{proxy,proxies,cache,temp,render-cache}/**. The size filter alone can't do it, because proxies can be large too.

Can one archive collect files from GoPro Cloud, Google Drive, Dropbox and a NAS? Yes. Create one workflow per source, point them all at the same archive, and give each its own path, such as gopro/{file_created_date}/{filename}.

• Blober Path Templates: Organize Files During Transfer
• Copy, Organize, or Move Files With Blober