Skip to content

Local Filesystem

The Local adapter reads and writes to your computer’s filesystem. This is particularly useful in the desktop app for backing up local files to cloud storage or syncing cloud files locally.

  • ✅ Browse folders and files via the desktop file picker
  • ✅ Create directories
  • ✅ Upload/copy files
  • ✅ Download/copy files
  • ✅ Delete files and directories
  • ✅ Move files
  • ✅ Get file metadata (size, dates, permissions)
  • ✅ Real-time file change detection
  • Blober Desktop App installed
  • Read/write permissions to the directories you want to access

Local paths are standard absolute paths on your operating system:

Windows:

C:\Users\YourName\Documents
D:\Backups\photos

macOS:

/Users/YourName/Documents
/Volumes/ExternalDrive/backups

Linux:

/home/yourname/documents
/mnt/backup
/media/yourname/external-drive

No credentials are required for the Local adapter. Access is based on the permissions of the user running the Blober desktop app.

  1. In Blober, go to Workflows => New Workflow
  2. Select Local as source or destination
  3. Click Browse to open the file picker
  4. Navigate to and select your folder
  5. The path will be populated automatically

Create a workflow to automatically backup your Documents folder to Azure Blob, S3, or other cloud storage.

Example:

  • Source: Local /Users/you/Documents
  • Destination: AWS S3 my-backup-bucket/documents/
  • Action: Copy

Sync your Google Drive or cloud storage files to a local folder for offline access.

Example:

  • Source: Google Drive My Files/Projects
  • Destination: Local /Users/you/Projects
  • Action: Copy

Copy files between different drives or directories on your computer.

Example:

  • Source: Local /Users/you/Downloads
  • Destination: Local /Volumes/ExternalDrive/Archive
  • Action: Move

Use local storage to test workflow configurations before running against cloud providers.

To avoid accidentally listing your entire filesystem, the Local adapter will not list anything when no start directory is specified. Browsing is always done via the UI file picker.

  • Access depends on NTFS permissions and UAC settings
  • Run Blober as Administrator if you need access to system directories
  • Right-click folder => Properties => Security to check permissions
  • You may need to grant Files and Folders or Full Disk Access permissions
  • Go to System Preferences => Security & Privacy => Privacy => Files and Folders
  • If prompted, click Allow when Blober requests folder access
  • Permissions are based on the user running the app and mount permissions
  • Check permissions with ls -la /path/to/folder
  • Fix permissions if needed:
    Terminal window
    chmod -R u+rw /path/to/folder
  • Exclude directories with many small files (1000s of files)
  • Check if antivirus is scanning files during operations
  • Ensure disk health is good (check SMART status)
  • Consider using filters to exclude temporary files
  • Ensure the drive is properly mounted
  • On Linux, check /media/ or /mnt/ for mount points
  • On macOS, check /Volumes/
  • On Windows, check if drive letter is assigned
  • Choose specific folders rather than entire drives
  • Avoid system directories:
    • Windows: C:\Windows, C:\Program Files
    • macOS: /System, /Library
    • Linux: /bin, /etc, /usr
  • Create dedicated backup folders for organization
  • Local operations are generally faster than cloud operations
  • For directories with thousands of files, use filters to limit scope
  • Consider excluding temporary files (.tmp, .log, cache directories)
  • Local storage never leaves your computer
  • No data is sent to Blober servers
  • Perfect for sensitive files that shouldn’t be uploaded to cloud

Blober can follow symbolic links:

  • Useful for organizing files across locations
  • Be careful with circular links (A => B => A)
  • Enable in workflow settings if needed
  • By default, hidden files (starting with . on Unix) may be hidden
  • Enable “Show hidden files” in settings to include them
  • Useful for backing up configuration files (.bashrc, .gitconfig)

Exclude certain file types from operations:

Example filters:

*.tmp # Temporary files
*.log # Log files
.DS_Store # macOS metadata
Thumbs.db # Windows thumbnails
node_modules/ # Dependencies

The desktop app respects OS-level sandboxing:

  • Limited access to system files
  • User explicitly grants folder access
  • No access to other applications’ data
  • Files stay on your computer (for local-to-local operations)
  • Cloud transfers go directly to the destination provider
  • Blober doesn’t store your files on its servers