How Blober Works, and Why It Runs on Your Machine

Blober is a desktop app that moves files between cloud storage providers and your own drives. It runs on your computer, talks directly to each provider, and never routes your files through a server in the middle. Because the work happens on your own machine, it keeps doing its job for as long as you need it.

That single choice, running on your machine instead of in someone else's cloud, shapes the rest of this page: how a transfer works, who can see your data, how Blober reaches providers that were never built for bulk transfers, and why it keeps working for years.

The short version

You sign in to your clouds inside Blober, pick what to move and where it should go, and press start. Blober reads from the source and writes to the destination using your own credentials, on your own hardware. Nothing about the transfer depends on a Blober account or a Blober server, because neither one is in the path.

How a transfer actually works

When you move files from one cloud to another, the data takes the short path:

Source cloud  ->  your computer (Blober)  ->  Destination cloud

Blober authenticates to each provider with your own credentials, streams the files from the source, and writes them to the destination. The bytes pass through your machine and nowhere else, because there is no Blober server in that path.

Many browser-based and hosted transfer tools take a longer path:

Source cloud  ->  a company's servers  ->  Destination cloud

In that model your files, and often your stored credentials, sit on infrastructure you do not control and cannot audit. Blober removes that hop.

Every job is built from three simple parts:

1. Source. Where the files come from: a provider, a path, and your credentials.
2. Destination. Where they should land: another provider or a local drive, with an optional path template to organize them.
3. Action. What to do: copy, move, or delete.

A saved combination of these is a workflow, and each run of a workflow is a task you can watch, pause, and resume. See Concepts for the full model.

Your credentials never leave your machine

Blober stores your provider keys and tokens in a local database on your computer. They are used to talk to your providers and are never uploaded to a Blober service, because there is no remote database to upload them to. The concepts guide lists the credential types Blober stores locally.

A storage key or an access token is not a limited transfer pass. It is the key to your whole account, with permission to read, write, list, and delete. When a hosted tool keeps that key on its servers, a breach of that company becomes a breach of your storage. With Blober there is no shared vault to breach.

It is download and upload, just automated

Mechanically, Blober does what you could do by hand: pull a file down from one place and push it up to another. It is the same operation your browser performs when you download a file and upload it again, only automated, parallelized, and able to skip files that already finished when you rerun an interrupted job.

That simplicity has a real benefit for anyone who has to answer for their data. Blober adds no new transfer provider to your data path, so it fits inside the controls you already have instead of widening your vendor surface. For a team running a security review (SOC 2, ISO 27001, or a GDPR data-processing assessment), the central question is narrower and easier to answer: apart from the source provider, the destination provider, and the machine running Blober, there is no relay service in the middle.

Blober does not change that picture, and that is the point.

It keeps working, for the long run

Because the work happens on your computer, Blober does not depend on a service staying online to keep functioning. There is no meter, no seat count, and no subscription renewal that can strand your files behind a paywall. Blober is a lifetime licence with lifetime updates, so the copy on your machine keeps working and keeps improving.

It also works when the network around the app does not. Blober talks to your providers directly, so it can retry a flaky connection or an interrupted job, and a rerun with skip-existing avoids sending files that are already at the destination. Your saved workflows stay on your machine, ready the next time you need them.

A tool that lives on your own hardware keeps working for the long run, with no subscription clock counting against it.

It reaches clouds that were never built for bulk transfer

Some services, especially consumer ones like GoPro Cloud and Google Photos, were never designed to let you move an entire library out at once. They expect you to use their own app, one screen at a time.

Blober connects to those services the same way their own apps do: through your own login, on your own machine, acting on your behalf. Because it runs locally, it can speak each provider's own dialect, including the quirks of services that have no formal export tool, without ever handing your session to anyone else. The result is that a multi-thousand-clip GoPro library can be queued in one workflow, and Google Photos can be used as a download-only source while that connector is in early access, into storage you control. See the Google Photos provider guide for the current capability limits.

A tool that lives on a central server has a much harder time here. Each of those consumer services has to be reached on behalf of every user at once, and the provider sees that traffic arriving in bulk from one company's servers, which is a pattern that can attract rate limits, geofencing, or blocks. Because Blober runs on your machine and connects from your own IP address, there is no shared relay address to block for every Blober user at once. Provider account limits can still apply, but the traffic is tied to your own login and your own connection.

Who it is for

• People leaving one cloud for another who want a clean, direct migration.
• Photographers, videographers, and creators moving large media libraries between providers.
• GoPro and Google Photos users who want their footage and photos somewhere they control.
• Teams and individuals who would rather not add another company to the list of services that can see their data.
• Anyone who would rather rely on a tool that lives on their own machine than a service they rent by the month.

How it compares to writing your own script

Capable command-line tools like rclone can also move data directly between clouds, and they are excellent in the right hands. The trade is your time: configuration files, credential management, and provider-specific flags, all from a terminal.

Blober is the same direct, local idea with the manual work removed. You connect a provider by signing in, browse your files visually, pick a destination, and run. There is no config file to maintain and nothing to debug at a command prompt. If you enjoy the terminal, a script is a fine path. If you would rather see your storage and click, that is what Blober is for.

Next steps

• New here? Start with Getting Started.
• Want the full list of supported services? See Providers.
• Ready to try it? Get Blober.