Working with objects

Use Copy to… or Move to… from a file's ⋯ menu, or select several files and use the Copy / Move buttons.

Both let you choose a destination bucket. By default the object stays in the bucket you're in; pick another and it lands there instead. The copy happens inside your storage provider — the bytes never travel through BucketPilot.

Only buckets on the same storage connection can be chosen, because a single copy is performed with a single set of credentials. To move data between two different connections — or into an SFTP server — create a migration job instead, which is built for that: it resumes, retries, and shows progress.

Where it lands. Type a full key to name the copy yourself. End the destination with a slash to drop the file into that folder under its own name, or enter a single / to put it at the bucket root. Selecting several files asks for a prefix instead, and each file keeps its own name beneath it.

Whole folders can be copied or moved too, including into another bucket — everything inside comes with them. Very large folders are better handled by a migration job, which resumes and retries; the file browser refuses a folder past its size cap and says so.

Drag files onto a bucket (or click Upload) and they go directly from your browser to your own storage over presigned URLs — BucketPilot never proxies the bytes. Uploading several files at once is a Pro feature; uploads are indexed the moment they finish, so they're searchable immediately.

Browser uploads need the bucket's CORS to allow them, and BucketPilot handles this for you: buckets created in BucketPilot get it on creation, and connected buckets get it automatically when you import them (with a fallback on the first upload). A bucket that already carries its own CORS rules is never touched — BucketPilot only adds the rule when there's none of its own.

From a bucket you can copy, move, rename, change storage class, edit tags, and download — including whole folders, recursively. Folder operations are capped at 5,000 objects; for anything larger, use a migration job.

Changing an object's storage class to GLACIER or DEEP_ARCHIVE is one-way without a restore, and the UI warns you before you do it. Archived objects can't be copied until they're restored — that's an AWS rule, not a BucketPilot limit.