How to Access Developer Console in Salesforce

What Is the Salesforce Developer Console?

If you work with Salesforce — whether you’re building automations, writing Apex code, or debugging flows — the Developer Console is the tool you’ll keep coming back to.

It’s Salesforce’s built-in integrated development environment (IDE). No downloads. No third-party plugins required. Just a browser-based workspace that lets you write, test, and debug code directly inside your Salesforce org.

According to Salesforce’s own developer statistics, there are over 9.3 million registered Salesforce developers worldwide, and that number continues to grow year over year. Whether you’re new to the platform or a seasoned pro, knowing how to quickly access the Developer Console is a skill that saves time and eliminates friction.

This guide walks you through every method to access it, what you can do once you’re inside, and answers the questions most people have when they’re getting started.

Why Use the Developer Console?

Before jumping into access methods, here’s what the Developer Console actually lets you do:

• Write and execute Apex code — test logic in real time without deploying a full release
• Run SOQL and SOSL queries — query your Salesforce data directly from the browser
• Debug logs — read detailed execution logs to find exactly where something broke
• Create and edit Lightning components, Visualforce pages, and Apex classes
• Run unit tests — validate that your code works before pushing to production

Salesforce reports that organizations using automation and custom development through tools like the Developer Console can reduce manual process time by up to 30%. Teams that actively use developer tools ship changes faster and catch bugs earlier.

How to Access the Developer Console in Salesforce

There are two main versions of Salesforce to consider: Lightning Experience (the modern UI) and Salesforce Classic (the older interface). The steps differ slightly, but both are simple.

Accessing the Developer Console in Salesforce Lightning Experience

This is the default interface for most Salesforce orgs today. Here’s how to get there:

Step 1 — Log in to your Salesforce org
Go to login.salesforce.com and sign in with your credentials.

Step 2 — Click your profile avatar
In the top-right corner of the screen, click on your user profile picture or avatar icon.

Step 3 — Select “Developer Console” from the dropdown
A dropdown menu will appear. Look for Developer Console in the list and click it.

Step 4 — Wait for the console to load
The Developer Console opens in a new browser window or tab. Depending on your org size and browser speed, this can take 5 to 20 seconds.

That’s it. You’re now inside the Developer Console.

Pro tip: If you don’t see “Developer Console” in your profile dropdown, it usually means your Salesforce user profile doesn’t have the “Author Apex” permission enabled. You’ll need a system administrator to grant it.

Accessing the Developer Console in Salesforce Classic

If your org is still running on Salesforce Classic:

Step 1 — Log in to Salesforce Classic
If you’re in Lightning, switch to Classic by clicking your name → Switch to Salesforce Classic.

Step 2 — Click your name in the top-right corner
In Classic, user options appear under your name (not a profile icon).

Step 3 — Click “Developer Console”
It appears in the dropdown just as in Lightning. Click it and a new window will open.

Opening the Developer Console via URL (Shortcut Method)

If you want to skip the menu navigation entirely, you can open the Developer Console directly with this URL pattern:

https://[your-org-domain].lightning.force.com/lightning/n/DeveloperConsole

Replace [your-org-domain] with your actual Salesforce domain. This is especially useful if you’re switching between multiple orgs throughout the day.

Accessing the Developer Console in a Sandbox

The process is identical in sandbox environments. Log in to your sandbox URL (typically [company]-[sandbox-name].sandbox.my.salesforce.com), then follow the same Lightning or Classic steps above.

Sandbox environments are where most developers and admins do their testing work. According to Salesforce’s release management best practices, over 70% of Salesforce projects involve at least one sandbox for testing before pushing changes to production.

What You Can Do Inside the Developer Console

Once you’re in, here’s a quick orientation of the key tabs and features:

Query Editor

This is where you run SOQL (Salesforce Object Query Language) queries to pull data from your org. Think of it like SQL — but for Salesforce objects.

Example query to retrieve 10 Account records:

SELECT Id, Name, Industry FROM Account LIMIT 10

Click Execute and results populate in a table below the editor.

Source Code Editor

The main text area where you write Apex classes, triggers, Visualforce pages, and Lightning Aura components. You can open existing files from the File menu or create new ones from scratch.

Logs Panel

Every time you execute code or load a page in Salesforce, a debug log is generated. The Logs panel displays these in real time. You can open any log to see a step-by-step trace of what executed, what failed, and why.

This is invaluable for debugging. Salesforce data shows that developers using structured debug logging resolve issues 2–3x faster than those relying on trial-and-error fixes.

Test Runner

Run Apex unit tests directly from within the console. You can run all tests in a class or individual test methods. Pass/fail results and code coverage percentages display immediately.

Salesforce requires a minimum of 75% code coverage before any Apex code can be deployed to production — making the test runner a critical part of any development workflow.

Common Reasons You Can’t Access the Developer Console

If the option doesn’t appear in your menu, here are the most likely causes:

Missing “Author Apex” permission
This permission must be enabled on your profile or via a permission set. Only a system administrator can grant it.

You’re using a non-developer user profile
Some standard profiles (like read-only or standard user) block access to developer tools by default.

Browser compatibility issues
The Developer Console works best in Chrome. If you’re having trouble loading it, try switching browsers or disabling extensions.

Your org has API access restrictions
Some enterprise orgs restrict developer tool access to certain IP ranges or profiles. Check with your Salesforce admin if you suspect this is the case.

You’re in a managed package context
If you’re working inside a managed package namespace, certain Developer Console features may be restricted depending on your org type.

Developer Console vs. VS Code with Salesforce Extensions

The Developer Console is great for quick tasks. But if you’re doing heavy development, many teams have migrated to Visual Studio Code with the Salesforce Extension Pack.

Here’s a quick comparison:

Salesforce’s own developer surveys indicate that over 65% of active Salesforce developers now use VS Code as their primary tool, though the Developer Console remains the go-to for fast queries, log analysis, and one-off fixes.

That said, for Salesforce admins (not full developers), the Developer Console is often the only tool they ever need.

Keyboard Shortcuts That Save Time

Once you’re inside the Developer Console, these shortcuts accelerate your workflow:

Small improvements in your daily workflow compound over time. If you’re spending even 10 minutes a day navigating menus instead of using shortcuts, that’s close to 40 hours per year of avoidable effort.

Conclusion

The Salesforce Developer Console is one of those tools that becomes second nature once you use it regularly. Whether you’re running a quick SOQL query, tracing a bug through debug logs, or testing a new Apex method — it’s all right there inside your browser, no extra software required.

The access process takes less than 30 seconds once you know where to look. Click your profile icon → Developer Console → done.

If you’re regularly working inside Salesforce-powered orgs to identify and reach your target accounts, there’s a much faster path to filling your pipeline. Rather than manually prospecting through CRM data, modern outbound teams use LinkedIn and cold email systems to reach decision-makers directly — with response rates of 15–25% compared to the 1–5% typical of traditional cold email alone.

That’s exactly what we build at SalesSo. We design complete outbound lead generation systems — from targeting and campaign design to scaling and optimization — so your calendar fills with qualified meetings while your team focuses on closing.

Book a Strategy Meeting with SalesSo →