File Organization Workflows for Creators, SMEs, and IT
Organization Must Fit the Work, Not Replace It
Section titled "Organization Must Fit the Work, Not Replace It"Most people do not need another platform where work must be imported, tagged, and maintained. They need files to move between the tools they already use without arriving as another unstructured dump.
Blober fits at that boundary. A source can be local storage, network storage, cloud drive, camera cloud, or object storage. A destination can serve editing, collaboration, delivery, or archive needs. Selection, filters, and path templates define what crosses that boundary and how it lands.
The examples below are starting points, not fictional one-size-fits-all systems. Each one names the pain, source scope, filter, path, and safe action.
Photographer: Separate Originals From Deliverables
Section titled "Photographer: Separate Originals From Deliverables"Pain: 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.
RAW archive workflow
Selection: the shoot folderFile Types: CR2, NEF, ARW, DNG, RAWAction: CopyDestination: object storageTemplate: originals/{file_created_date}/{file_dir}/{filename}Client delivery workflow
Selection: the same shoot folderInclude: **/*.{jpg,jpeg,png,tif,tiff}Exclude: **/{preview,previews,draft,drafts}/**Action: CopyDestination: client cloud folderTemplate: delivery/{file_dir}/{filename}One source supports two outcomes without moving the working library.
Videographer: Protect Masters, Ignore Rebuildable Proxies
Section titled "Videographer: Protect Masters, Ignore Rebuildable Proxies"Pain: Original camera media, proxies, render caches, review files, and masters are mixed across nested project folders. Proxy media may be large but replaceable.
Selection: all completed project foldersInclude: **/*.{mp4,mov,mxf,braw,r3d}Exclude: **/{proxy,proxies,cache,temp,render-cache}/**Size: LargeAction: CopyTemplate: masters/{file_created_date}/{file_dir}/{filename}The glob exclusion is more meaningful than size alone. A large proxy is still a proxy. Combining path conventions, type, and size produces a better candidate set.
YouTube or Social Creator: Consolidate Several Services
Section titled "YouTube or Social Creator: Consolidate Several Services"Pain: 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 to 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 do not need to integrate with one another. Blober connects to each endpoint, and the common destination layout provides consistency.
Design Studio: Collect Approved Exports
Section titled "Design Studio: Collect Approved Exports"Pain: Editable design sources and exported assets sit beside drafts, autosaves, and review versions. Developers or clients need only approved SVG, PNG, PDF, and WebP files.
Selection: approved campaign or client foldersInclude: **/*.{svg,png,pdf,webp}Exclude: **/{draft,drafts,review,autosave}/**Action: CopyTemplate: assets/{file_ext}/{file_dir}/{filename}Use visual folder selection for approval state when possible. It is safer to select a known Approved folder than to infer approval from every possible filename.
Agency: Standardize Client Handoffs
Section titled "Agency: Standardize Client Handoffs"Pain: 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}.
The workflow can be edited for each client's credentials and destination while preserving the agency's selection discipline.
Small Business: Archive Records Without Moving Daily Work
Section titled "Small Business: Archive Records Without Moving Daily Work"Pain: A shared drive mixes current records, old invoices, scans, spreadsheets, and temporary office files. Staff need the shared drive unchanged, but the business needs a second durable copy.
Selection: Finance, Contracts, ReportsInclude: **/*.{pdf,doc,docx,xls,xlsx,csv}Exclude: **/{temp,autosave,draft,drafts}/**Action: CopyTemplate: business-records/{file_ext}/{file_modified_date}/{file_dir}/{filename}The date and type layers make future browsing easier while {file_dir} retains departmental context beneath each selected folder.
Research Team: Separate Datasets From Documentation
Section titled "Research Team: Separate Datasets From Documentation"Pain: 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:
- Large dataset archive: size Large, relevant binary/data extensions, destination object storage.
- Research documentation: PDF, Markdown, notebooks, CSV summaries, destination collaboration drive.
Preserve {file_dir} so experiment and study structure survives both transfers.
IT Team: Back Up What Cannot Be Rebuilt
Section titled "IT Team: Back Up What Cannot Be Rebuilt"Pain: Application trees contain source, configuration, uploaded assets, dependencies, caches, builds, and logs. Copying everything increases cost and recovery noise.
Selection: application and service foldersInclude: **/*Exclude: **/{node_modules,cache,tmp,temp,dist,build,coverage}/**Action: CopyTemplate: systems/{file_dir}/{filename}Adjust exclusions to the actual recovery plan. Never exclude a directory merely because its name sounds generated if the organization cannot rebuild it.
Enterprise Migration: Split a Large Move Into Verifiable Rules
Section titled "Enterprise Migration: Split a Large Move Into Verifiable Rules"Pain: A monolithic migration is difficult to estimate, validate, and retry. 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 has a smaller preview, clearer ownership, and a destination path aligned to that data class. This is often easier to audit than one huge transfer rule.
Personal Archive: Make Old Media Browsable
Section titled "Personal Archive: Make Old Media Browsable"Pain: Family photos and videos are spread across disks and clouds with inconsistent folders.
Selection: camera uploads and old media foldersInclude: **/*.{jpg,jpeg,heic,png,mp4,mov}Action: CopyTemplate: personal-media/{file_created_date}/{file_dir}/{filename}Preview the creation dates. A cloud provider may report upload time rather than original capture time. If dates are poor, use {file_dir} and filenames instead of forcing a misleading chronology.
The Common Safety Pattern
Section titled "The Common Safety Pattern"Across every profession:
- Select the smallest meaningful scope.
- Use Copy first.
- Combine only filters that express a real rule.
- Preserve
{file_dir}when project hierarchy matters. - Inspect Preview & Summary.
- Verify actual destination files.
- Scale or move only after the result is trusted.
For technical details, read the complete path-template guide. For operational choices, read Copy As-Is, Organize During Backup, or Reorganize With Move.
