Salesforce Inspector: What It Does, Who It Is For, and What It Cannot Do

Every Salesforce admin has a deal with the org. The deal is this: the org holds everything, but it does not give it up easily. Fields you need are buried behind layouts that were designed for reps, not for the people who have to operate the system. Running a query means opening the developer console, which means switching tabs, which means losing the context you were trying to investigate in the first place. Salesforce Inspector was built to cancel that deal.

Salesforce Inspector is a browser extension that lets Salesforce admins and developers view every field on any record, run SOQL queries, inspect object and field metadata, and export or import data without leaving the browser. It does one job, and it does it well. The version most people use today is Salesforce Inspector Reloaded, an open-source fork maintained independently of Salesforce by a community that has built on the original for years. The project has crossed tens of thousands of users. It is the free tool of choice for anyone who operates the Salesforce org rather than selling in it.

This guide covers both sides of that question: what it does, and what it does not.

What does Salesforce Inspector do?

Pop open any Salesforce record with the extension active and a small icon appears in the corner of the browser. Click it and a panel opens alongside the page, showing every field on that record, including the ones hidden by the page layout, the ones marked internal-only, the ones your admin buried three permission sets deep. You see the raw data the way the database sees it. No switching tabs, no running a report, no asking someone who has a different permission level.

Think of it as a flashlight pointed into the back of the drawer. The record was always there; the tool removes the need to move furniture to reach it.

From the same panel you can switch to the SOQL editor and write a query against any object, instantly, without opening the developer console. You can browse field metadata, see API names, check field types, confirm which fields exist on an object before you build a validation rule. You can export query results to CSV, or import data directly. The full scope of Salesforce Inspector chrome work covers four modes: field viewer, SOQL query, metadata browser, and data loader.

That last point matters more than it sounds. A tool that keeps you on the page you are already on is a tool that preserves the context you came to investigate. The classic admin workflow before Inspector was to see something odd in a record, open a new tab to run a query, lose the reference point, and half-remember what you were checking. Inspector closes that loop by making the query happen where the question arose.

The Salesforce developer documentation at https://developer.salesforce.com/ covers the underlying SOQL and SOSL query languages Inspector exposes. If you are learning the query syntax, that is the canonical reference. Inspector makes those queries available from the sidebar of any record rather than the developer console.

Who should use Salesforce Inspector Reloaded?

Admins and developers. Full stop.

The tool was built for people who operate the org, configure it, debug it, and maintain it. A Salesforce admin checking a validation rule, a developer tracing a flow, a solution architect confirming field values after a data migration, a RevOps analyst spot-checking record states: these are the users Inspector was made for. If your job is understanding what is inside the org, Salesforce Inspector Reloaded is one of the best free tools you can install. It earns its place in any Salesforce Chrome extension toolkit and consistently ranks among the highest-rated entries in roundups of the best Salesforce Chrome extensions.

A sales rep who wants to update a field faster, or a manager who wants to know why deals stall, is not the audience. Not because the tool is hard to use, but because the job it does is not their job. The org reading job and the rep behavior job are separate problems, and they require separate tools.

What Salesforce Inspector cannot do

Here is the honest turn, and it is worth stating plainly.

Salesforce Inspector reads the org. It does not change what reps do inside it.

You can use it to confirm that every deal in the pipeline has a next step field populated. What you cannot do is make the rep fill that field in the moment they should, surface the playbook when they are about to miss a discovery step, or tell a manager on Monday morning which reps followed the process and which skipped it. Those are not Inspector problems. They are behavior problems, and Inspector was never built to solve them.

This distinction matters because the two jobs get confused. A team with a clean org and a well-configured field layout still has the behavior problem if reps are not running the process. A fast SOQL query tells you what the data says; it does not change what generated the data. Reading is one job. Behavior is another.

Accurate.

In our survey of 198 sales leaders for The State of Sales Enablement, 89 percent of teams had a defined process and 36 percent saw it followed, and guidance in the flow of work split quota attainment from 15 percent to 49 percent. No metadata inspector touches that variable. The gap between a process that exists in the org and a process that reps run is the gap the tool cannot close.

What closes the behavior gap?

The behavior layer. Supered is the behavior layer that rides alongside Salesforce: it surfaces the next step of your process at the deal, delivers the playbook in the flow of work, captures the CRM update as a byproduct, and makes adherence visible deal by deal. When Inspector shows you that a next-step field is blank on forty percent of open opportunities, Supered is the tool that makes blanks rare in the first place, because the rep sees the required step in the moment they are on the record, not after the fact when a manager runs a query. The full argument is in the Salesforce Chrome extension guide and the broader pattern is in the sales process guide.

The two tools are not in competition. An admin who uses Inspector to operate the org and a team that uses Supered to run the process are doing different things, and both things matter. The mistake is believing the first one is a substitute for the second.

What to use and when

A recap of where each tool wins:

• Salesforce Inspector Reloaded. Install it if you are a Salesforce admin or developer who needs to query records, inspect metadata, and export data without a separate environment. Free, open-source, and actively maintained. The best tool in its category by a wide margin.
• The native Salesforce developer console. Still useful for complex scripting, anonymous Apex execution, and debugging flows. Inspector does not replace it for everything, only for the most common query and field inspection work.
• The behavior layer for process adherence. If the question is whether reps are following the sales process and what to do when they are not, that is a different purchase and a different category. Inspector tells you the state of the data. The behavior layer changes the state of the rep.

The right set of salesforce inspector chrome tools depends entirely on which job you are trying to do. For reading and operating the org, Salesforce Inspector Reloaded is the free standard. For changing what reps do next, look at the behavior layer.

The sales productivity guide covers how these categories fit together in a larger stack. Book a demo to see Supered running against a real process and understand exactly what the behavior layer adds where Inspector stops.