Integrated Development Environment (IDE)
An Integrated Development Environment (IDE) for Salesforce is the code editor that developers use to build, debug, and deploy Apex classes, triggers, Visualforce pages, Lightning Web Components, Aura Components, and metadata configurations to a Salesforce org.
Definition
An Integrated Development Environment (IDE) for Salesforce is the code editor that developers use to build, debug, and deploy Apex classes, triggers, Visualforce pages, Lightning Web Components, Aura Components, and metadata configurations to a Salesforce org. Modern Salesforce IDE work centers on Visual Studio Code with the Salesforce Extensions Pack, paired with the Salesforce CLI (sf) for command-line operations. Earlier generations of the Salesforce IDE included the Force.com IDE (Eclipse-based, retired in 2018) and the in-browser Developer Console (still maintained but rarely the primary editor).
The IDE handles the full development loop: project creation against a Dev Hub, source pulling and pushing between local files and the org, debugging via Apex Replay Debugger, testing via the Apex Test Runner integration, and metadata deployment via Change Sets, Metadata API, or DevOps Center. The IDE choice has converged: Visual Studio Code with Salesforce Extensions is now the supported, official tool, and Salesforce documentation defaults to it for every developer workflow. Custom IDEs (IntelliJ with Illuminated Cloud, custom SFDX wrappers) still exist and are popular with certain developer communities.
The Salesforce IDE landscape from Force.com IDE to VS Code
VS Code with Salesforce Extensions Pack
The Salesforce Extensions Pack for VS Code is the official supported IDE. It bundles Apex syntax highlighting, Lightning Web Component support, Aura Component support, the Salesforce CLI integration, the Apex Test Runner, the Apex Replay Debugger, and SOQL Builder. Install once via the VS Code Marketplace; the extensions auto-update with Salesforce''s schedule.
Salesforce CLI (sf) as the foundation
The Salesforce CLI (sf, formerly sfdx) is the command-line tool every IDE workflow runs on top of. It handles authentication (sf org login), source operations (sf project deploy/retrieve), test execution (sf apex run test), and dozens of other commands. The VS Code extensions are essentially a GUI wrapper around CLI calls; experienced developers often mix command-line use with editor work.
Project structure and SFDX format
Modern Salesforce projects use the SFDX source format: files organized into folders by metadata type (classes, triggers, lwc, aura, objects), with a sfdx-project.json manifest at the root. The format supports source tracking against scratch orgs and is the foundation of modern packaging (Unlocked Packages, Second-Generation Managed Packages).
Force.com IDE retirement
The Force.com IDE was an Eclipse plug-in that served as the official IDE from 2010 to 2018. Salesforce retired it in favor of VS Code and the SFDX toolchain because Eclipse adoption among new developers had collapsed. Existing projects using the Force.com IDE format must migrate to the SFDX source format, which the cli supports via sf project convert source.
Developer Console
The Developer Console is the in-browser IDE that ships with every Salesforce org. It supports editing Apex, executing anonymous Apex, running queries via the Query Editor, and inspecting debug logs. It is the fastest path for quick edits but lacks the depth of VS Code. Most professional developers use the Console for debugging and the Salesforce-side workflow but not for primary code authoring.
Apex Replay Debugger
The Apex Replay Debugger inside VS Code lets developers step through executed Apex code line by line using a recorded debug log. The developer enables the trace flag, executes the code that fails, downloads the log, and opens it in the debugger. Breakpoints, variable inspection, and step-over all work; the experience is close to a traditional debugger.
Source-tracked vs. non-source-tracked orgs
Scratch orgs and developer sandboxes can be source-tracked, meaning the org tracks which metadata has changed since the last pull or push. The IDE uses source tracking to keep the local project and org in sync without manual diff work. Production orgs are not source-tracked, so deployment uses the traditional Metadata API model with explicit manifests.
Set up the modern Salesforce IDE stack
The full setup takes about an hour for a fresh developer machine. Most of the time is downloads; the actual configuration is minimal.
- Install Visual Studio Code
Download from code.visualstudio.com. The free download is the full IDE.
- Install the Salesforce Extensions Pack
Open VS Code, Extensions, search for Salesforce Extension Pack. Install the bundle.
- Install the Salesforce CLI
Download from developer.salesforce.com/tools/sfdxcli. The installer adds the sf command to your shell.
- Authenticate against your org
Run sf org login web -a your-org-alias. A browser opens; complete the OAuth flow. The CLI stores the refresh token locally.
- Create or retrieve a project
Either sf project generate to create a new SFDX project, or open an existing project folder and pull metadata via sf project retrieve start.
- Configure debugger and test runner
Apex Replay Debugger and Apex Test Runner are part of the extensions; they configure automatically once a project is opened.
- Force.com IDE projects do not work with VS Code without conversion. Use sf project convert source to migrate before opening.
- Salesforce CLI authentication uses local OAuth tokens. Loss of the developer machine means re-authenticating; tokens cannot be recovered remotely.
- Source tracking works on scratch orgs and developer sandboxes only. Production deployments use manifest-based deploys and require explicit destructive changes for deletions.
- IDE updates ship monthly alongside Salesforce releases. Stay on the latest version to avoid bugs the Salesforce team has already fixed.
Trust & references
Straight from the source - Salesforce's reference material on Integrated Development Environment (IDE).
- Salesforce DX Developer GuideSalesforce Developers
Hands-on resources to go deeper on Integrated Development Environment (IDE).
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What's the modern Salesforce IDE?
Q2. What's the old Salesforce IDE?
Q3. Where do serious Salesforce DX workflows happen?
Discussion
Loading discussion…