S3 file browser options compared, from the AWS console to Cyberduck, S3 Browser, Transmit and web workspaces
There are four ways to browse Amazon S3 with a file manager instead of the command line. This guide compares the AWS console, Storage Browser for S3, the desktop clients and a web workspace on cost, setup, platform and how each one signs in to AWS.

The AWS console and desktop clients such as Cyberduck, CS Browser and Transmit are the right S3 file browsers for people who already have AWS credentials, and Storage Browser suits teams building their own React app; when the people who need the files are not engineers, a web workspace that holds one scoped IAM role is simpler than giving each of them an AWS identity.
An S3 file browser, also called an S3 explorer or S3 file manager, shows the objects in a bucket as folders and files you can open, upload and download. You can use the AWS console in a web browser, build the Storage Browser for S3 component into your own app, install a desktop client such as Cyberduck, S3 Browser or Transmit, or use a web workspace such as BucketDesk that connects to the bucket through an IAM role.
Which one fits depends on two things: who needs the files, and how they will sign in to AWS. An engineer who already has AWS credentials is well served by the console or a desktop client. A finance, legal or operations team that only needs to find, open and share files usually is not. The prices and platforms below are from each vendor's site as of October 2026.
The four ways to browse S3 at a glance
- AWS console: included with your AWS account, runs in any browser, every person needs an IAM identity with console access.
- Storage Browser for S3: an open source React component from AWS that you add to your own web app and host yourself, with sign-in built by your team.
- Desktop clients: Cyberduck (macOS and Windows, free with donations), S3 Browser, now named CS Browser (Windows only, Pro licence for business use), Transmit 5 (macOS only, $45). Each person signs in with their own AWS credentials.
- A web workspace such as BucketDesk: runs in the browser, connects to the bucket through one scoped IAM role, and people sign in to the workspace instead of to AWS.
How do I view an S3 bucket in a browser?
The quickest way is the S3 console. Sign in to the AWS Management Console, open S3, choose General purpose buckets and pick the bucket. You see its folders (prefixes) and objects, and you can select an object to download it or open its details page.
There are two limits worth knowing. The console downloads one object at a time, and whether a file shows in the tab or lands in Downloads depends on its Content-Type and Content-Disposition headers. For anyone outside your AWS account, the console route is a presigned URL: the console can create one that lasts up to 12 hours, and anyone holding it can download the object until it expires.
If people who do not work in AWS need to browse the bucket every day, use one of the other three options below instead of handing out console access.
Choosing a browser-based S3 file viewer for business documentsHow to preview files in Amazon S3 without downloading them
The AWS console
The S3 console is complete and comes with every AWS account. It shows storage class, metadata, versions and permissions, and it is where engineers change bucket settings. For an engineer checking one file, nothing is faster to reach.
It was built for people who run the AWS account. Every user needs an IAM user or an IAM Identity Center assignment with console access, and the screens they land on include settings they should not touch. Limiting a person to one folder means writing an IAM policy. Downloading several files at once means the AWS CLI or CloudShell rather than the console.
Storage Browser for Amazon S3
Storage Browser for S3 is an open source component in the AWS Amplify React library. You add it to your own web or intranet application, and it gives your signed-in users a file browser for list, download, upload, copy and delete. AWS maintains the component; your team hosts the app, wires up authorization and sets CORS on each bucket.
It works only in React apps, and it cannot reach objects in S3 Glacier Flexible Retrieval, S3 Glacier Deep Archive or the Intelligent-Tiering archive tiers. If you already have a React product and a developer to own it, it is the right choice for adding S3 file management to that product. Teams building that kind of app often add document extraction too; Bedrock Data Automation for S3 documents covers that side. For a managed option, AWS points to Transfer Family web apps.
Cyberduck
Cyberduck is open source under the GPL and runs on macOS and Windows. The download is free; a donation of at least $10 gets a registration key that turns off the donation prompt, and you can also buy it from the Mac App Store or the Microsoft Store. It speaks many protocols besides S3, which makes it a favourite for people who also manage FTP, SFTP or other cloud storage.
For S3 it supports long-term access keys, profiles from the AWS credentials file, IAM Identity Center, and temporary credentials from STS with optional MFA. That flexibility is a strength for engineers. For a business user it means someone has to create one of those identities and set it up on their computer.
S3 Browser, now CS Browser
The long-running Windows client from s3browser.com is now called CS Browser. It is Windows only. The free edition is licensed for personal use only, so commercial, government and other business use needs Pro, which costs $49.99 per computer for a lifetime licence with one year of upgrades and support.
It supports AssumeRole with an external ID and IAM Identity Center as well as access keys. As with Cyberduck, each person still connects as their own AWS identity.
Transmit 5
Transmit from Panic is a polished file transfer app for the Mac. It handles FTP, SFTP, WebDAV and S3, including S3 Signature Version 4 and AWS GovCloud.
Connections use an IAM user's access key ID and secret, optionally with an AWS profile or an IAM role on top. It costs $45 after a free 7-day trial and requires macOS 13 or later, so it is not an option for Windows users.
Is S3 Browser safe?
S3 Browser, now CS Browser, is a long-running commercial product, and its documentation says it always encrypts stored access keys before writing them to disk. By default it uses a key built into the application; you can set your own master password per account, which it asks for when it needs that account and cannot recover if you forget it. Turn the master password on.
The bigger risk with any desktop S3 client is the credential you give it. Long-term access keys on a laptop work from anywhere until someone rotates them. Download the app only from the vendor's site, never use root account keys, and prefer AssumeRole or IAM Identity Center with a policy limited to the buckets that person needs. The same advice applies to Cyberduck and Transmit.
Credentials or an IAM role: the security model behind each option
The console and the desktop clients sign each person in as an AWS principal: an IAM user, an Identity Center user or an assumed role. Someone has to create that identity, scope it to the right buckets in IAM, and remove it when the person leaves. "Legal can see the contracts folder but not finance" becomes a policy an engineer writes and maintains.
Storage Browser leaves the model to you. AWS documents three options: Amplify Auth, built on Cognito, for customers and partners; IAM principals with S3 Access Grants; or IAM Identity Center with S3 Access Grants for a whole company. A workspace such as BucketDesk takes the other path. The workspace holds one scoped role in your account, people sign in to the workspace, and their access is set by a workspace role rather than an IAM policy. What a bucket needs before it connects lists the details.
- Per-person AWS identity: AWS console, Cyberduck, CS Browser, Transmit.
- Your own app's sign-in, configured by your developers: Storage Browser for S3.
- One scoped IAM role for the whole team, people sign in to the app: a hosted workspace such as BucketDesk.
How to choose
Pick by who will use it, not by feature count. Many teams end up with two: engineers keep the console or a desktop client, and everyone else uses a workspace on the same buckets. If that workspace also answers questions about documents, plan the AI budget early with these document AI spending controls.
- One engineer checking a bucket now and then: the AWS console.
- One technical person moving files regularly: Cyberduck on Mac or Windows, or Transmit on a Mac.
- A Windows team that already manages IAM well: CS Browser Pro, with AssumeRole or IAM Identity Center rather than long-term keys.
- A React product that needs S3 file management for its own users: Storage Browser for S3.
- Non-technical staff who need to find, preview and share files: a workspace, so nobody outside engineering needs an AWS identity.
A browser workspace for people who do not work in AWS
BucketDesk is a web workspace on top of your S3 buckets. You connect a bucket by deploying a scoped IAM role with CloudFormation; BucketDesk assumes it with an external ID for temporary credentials. Your staff sign in to BucketDesk, so nobody outside engineering needs an AWS identity, and files are read by range straight from your bucket.
- Connect a bucket
deploy the CloudFormation role in your account, and remove the role to end access.
- Open files in the browser
PDF, images including HEIC, text, HTML and Markdown on every plan; Word, Excel, PowerPoint, audio and video on Standard and Ultra.
- Share without AWS
on Standard and Ultra, send a link that expires and can be revoked; recipients enter a six-digit code sent to their email and every open is logged.
See the S3 file browser for teamsSecure AWS access with IAM roles and external IDsSee every feature with its plan and limitsPlans and pricingCompare these steps with the AWS ConsoleCompare CloudBerry Explorer and BucketDesk workflowsCompare Cyberduck and BucketDesk workflowsCompare S3 Browser and BucketDesk workflowsCompare Transmit and BucketDesk workflows
BucketDesk is built for finding, previewing and sharing files. If an engineer needs to move a terabyte between buckets or script transfers, Cyberduck, CS Browser or the AWS CLI is the better choice, and many teams keep both on the same buckets.
Minimum is free for one bucket and one viewer. Standard is $100 a month with unlimited buckets and viewers. Ultra is $350 a month, adds uploads, delete with confirmation and Glacier restore, and has a one-month free trial.
Primary sources
- AWS: Downloading objects (console, one object at a time, presigned URLs up to 12 hours) ↗
- AWS: Working with Storage Browser for Amazon S3 ↗
- AWS: Setting up Storage Browser for S3 ↗
- AWS: Configuring Storage Browser for S3 (CORS) ↗
- AWS: Storage Browser for S3 feature page ↗
- Cyberduck: home page ↗
- Cyberduck: download and donations ↗
- Cyberduck docs: Amazon S3 authentication ↗
- CS Browser: Pro license ↗
- CS Browser: free vs Pro ↗
- CS Browser: encryption of stored access keys ↗
- CS Browser: Amazon S3 via AssumeRole ↗
- CS Browser: Amazon S3 via AWS SSO ↗
- Panic: Transmit 5 ↗
- Panic help: IAM roles for Amazon S3 in Transmit ↗
- Panic help: transferring files on S3 ↗
Discussion
0 comments · open to guests · moderatedLiked this? Get the next article by email. No schedule, no digest, one click to leave.