Frequently Asked Questions (Beta)

Web Console is Salesforce’s modern, browser-based IDE embedded directly in Salesforce workflows. It’s designed to help developers debug, inspect, edit, and validate without switching tools. Web Console also closes key Developer-Console gaps with features, such as Debug Logs Viewer, Query Plan Inspector, SOQL execution, Anonymous Apex, and quick in-context Apex edits.

Only users with the appropriate admin permissions can enable or disable Web Console, access the Web Console Setup page, or change the default IDE setting for the org. Individual users can’t enable or disable it for themselves.

Web Console is available in Developer, Enterprise, Unlimited, Performance, and Professional editions, but the available functionality varies. For instance, full Apex development and feature access is available on active production orgs, such as Developer and Enterprise. In contrast, Professional orgs have restricted access to code and features.

After Web Console is enabled, the Web Console menu appears in the Setup gear menu. Refer to Launch Web Console to learn about other entry points, including Scheduled Jobs, Apex Class, and Apex Triggers.

Refer to Developer Console Vs Web Console for details.

Refer to Web Console Vs Agentforce Vibes IDE for detailed differences between the two products.

The extensions in Web Console come prepackaged. You can’t install or search for an extension on the Visual Studio MarketPlace. To see a list of installed extensions, click the ellipsis (…) on the Extensions Installed panel on the left side, and select Show Running Extensions.

Web Console is designed to preserve production guardrails. In production orgs, Apex remains read only, with users able to inspect code but not directly modify it. In non-production orgs, developers can use Web Console for quick fixes, testing, and validation workflows.

While you are actively editing, your browser holds a temporary working copy, but all saved files reside within your Salesforce org’s existing cloud storage infrastructure. The file storage follows your established data residency rules. Storage location depends on your specific setup.

  • Hyperforce Instances: Files are stored within your specific regional instance (For example, India).
  • Traditional Instances: Files are stored in your standard instance location (For example, NA, EMEA, or AP).