Salesforce Workbench is a free, web-based toolkit that lets admins and developers query, change and deploy Salesforce data and metadata directly through the Salesforce APIs. It is an open-source community project, not supported by Salesforce, and its own README now says it is in maintenance only mode: no new features and no new security fixes.
This guide was first published in 2021 as "How to Use Salesforce Workbench". It has been rewritten for 2026: what Workbench does, how to use it without breaking things, and when a supported tool is the better choice.
What is Salesforce Workbench?
Workbench is an open-source web app that talks to Salesforce's APIs, so you can query, load and deploy without the normal user interface. Workbench describes itself as a powerful, web-based suite of tools for administrators and developers. According to its wiki, it works through the Partner, Bulk, REST, Streaming, Metadata and Apex APIs, so it can reach things the Salesforce user interface hides. A shared copy runs at workbench.developerforce.com, and the code is open source under the BSD-3-Clause license on GitHub.
What can you do in Workbench?
Workbench covers queries, data changes, metadata and API utilities.
| Area | What Workbench offers | Typical use |
|---|---|---|
| Queries | SOQL queries (including a matrix view) and SOSL search | Check data an admin report can't show, test a query before putting it in code |
| Data | Insert, update, upsert, delete, undelete and purge; single-record actions; bulk loads through the Bulk API; permanent hard delete | Small fixes and one-off loads |
| Metadata | Describe, retrieve and deploy; browse metadata types and components | Inspect configuration, move a package between orgs |
| Utilities | REST Explorer, Execute (anonymous Apex), Streaming API push topics | Call an endpoint by hand, run a short script, test events |
How to log in to Salesforce Workbench
Go to the site, choose production or sandbox and an API version, then log in with Salesforce.
- Go to workbench.developerforce.com.
- Choose the environment: Production or Sandbox.
- Choose the API version. The wiki notes that Workbench is designed and tested for the latest API version and offers older ones only as a convenience.
- Accept the terms and log in with your Salesforce credentials (Workbench supports OAuth 2.0 login).
Log in to a sandbox first whenever you plan to change anything. Workbench acts with your full Salesforce permissions. You can switch API version later without logging out, from the session settings.
How to run a SOQL query in Workbench
Open Queries, choose SOQL Query, build or type the query and run it.
- Open Queries → SOQL Query.
- Pick the object, then the fields, or type the query directly, for example
SELECT Id, Name, StageName FROM Opportunity WHERE CloseDate = THIS_QUARTER. - Choose to view the results in the browser or download them as a file.
- Add a
LIMITwhile you test, so a mistake doesn't pull a million rows.
Salesforce's SOQL and SOSL reference covers the query language itself.
How to update records without breaking things
Export first, test in a sandbox, change the smallest set of records and keep a log.
For inserts, updates and upserts, Workbench's Smart Lookup option, described in its wiki, resolves external IDs or lookup values to Salesforce record IDs through related objects, for single records and CSV files. That saves a separate query to look up IDs, for example when you reassign case owners from a list of names.
- Export first. Query the records you are about to change and save the file, so you can put them back.
- Test in a sandbox. Run the same update there and check automation, flows and validation rules behave as you expect.
- Change the smallest set. Filter tightly and check the record count before you confirm.
- Avoid hard delete and purge in production unless you are certain: hard-deleted records skip the Recycle Bin.
- Log what you did. Workbench keeps no change history for you; note the file, the time and the reason.
Is Salesforce Workbench safe to use in 2026?
It still works, but treat it as a convenience tool, not part of your production process. Three facts from the project itself:
- Its README says it is not a supported product of, or supported by, salesforce.com.
- The same README says it is in maintenance only mode: no new features, and no new security issues will be fixed.
- Its wiki was last edited on 26 October 2020.
Salesforce itself says the same. Its release note Replace Workbench With Salesforce Developer Tools says Salesforce doesn't maintain Workbench, can't fix its issues or bugs, and can't assure that it will be available in the future, and it recommends Code Builder, the Salesforce CLI and the Salesforce extensions for VS Code instead.
For a quick query or a look at metadata in a sandbox, Workbench is fine. For anything regular, large, audited or in production, use a supported tool.
Workbench vs Data Loader vs the Salesforce CLI
Use Workbench for quick checks, Data Loader for bulk data, and the Salesforce CLI or VS Code for anything scripted or deployed.
| Tool | Supported by Salesforce | Best for |
|---|---|---|
| Workbench | No (open-source, maintenance only) | Quick queries, metadata inspection, one-off fixes in a sandbox |
| Data Loader | Yes | Large or repeated imports and exports, with a command-line mode for scheduled jobs |
| Salesforce CLI | Yes | Scripted, version-controlled data and metadata work and deployments |
| Salesforce extensions for VS Code, Code Builder | Yes | SOQL, anonymous Apex and metadata work in an editor; Salesforce's recommended replacement |
| Developer Console query editor | Yes (built in) | Simple SOQL with nothing to install |
Our guides to the Data Loader and the Salesforce CLI cover the supported options step by step, and what is Salesforce metadata explains what you are deploying. For metadata deployments, the CLI and the Metadata API behind it give you repeatable, reviewable releases that Workbench's manual deploy can't.
Getting help
If your team relies on Workbench for regular data fixes or deployments, that is usually a sign the process needs a supported, repeatable home, such as a release pipeline (see Salesforce DevOps). Techila is a Salesforce Summit Partner; our managed services team runs data operations and release management for Salesforce orgs. Talk to us about moving routine Workbench jobs onto Data Loader or the CLI.
Frequently asked questions
Is Salesforce Workbench free?
Yes. Workbench is an open-source project under the BSD-3-Clause license, and a shared copy is hosted at workbench.developerforce.com. There is no licence fee, but there is also no vendor support.
Is Salesforce Workbench supported by Salesforce?
No. The project's own README says Workbench is not a supported product of, or supported by, salesforce.com. It also says the project is in maintenance only mode: no new features and no new security fixes.
Is Salesforce Workbench safe to use?
Use it with care. It acts with your full Salesforce permissions, it can hard-delete records, and its own README says no new security issues will be fixed. Prefer Data Loader or the Salesforce CLI for regular or production work, and keep Workbench for quick inspection.
What can I do in Salesforce Workbench?
Run SOQL queries and SOSL searches; insert, update, upsert, delete, undelete and purge records, including in bulk; describe, retrieve and deploy metadata; call the REST API through the REST Explorer; execute anonymous Apex; and test Streaming API push topics.
What should I use instead of Workbench?
Data Loader for large or repeated imports and exports, the Salesforce CLI for scripted and version-controlled data and metadata work, and the Developer Console's query editor for simple SOQL with no setup.