Welcome
Thank you for using Salesforce Field Inspector, a Chrome and Edge extension that lets you hover over any field on a Salesforce Lightning record page to instantly see its API name, type, formula, picklist values, history tracking, and more.
Features
- 🔍 Instant field metadata on hover — no Setup navigation required
- 📋 One-click Copy API Name to clipboard
- 🧮 Full Formula body in a scrollable code block
- 📦 Picklist values with a link to view all in Salesforce Setup
- 🔗 Lookup & Master-Detail — referenced object, relationship name, cascade delete
- 📊 Precision & Scale for Currency, Number, and Percent fields
- ✅ Field access flags — Required, Updateable, Createable, Unique, External ID, Encrypted
- 🕒 History Tracked status via Salesforce Tooling API
- 🔒 Check FLS ↗ — opens Salesforce Inspector with a pre-built FieldPermissions SOQL
💡 Built to complement Salesforce Inspector Advanced and Salesforce Inspector Reloaded. Use this extension to identify a field instantly on the page, then hand off to Salesforce Inspector for deeper FLS analysis via the Check FLS ↗ button.
Extensionv1.0.0
ChromeMV3
PlatformChrome · Edge
Get Started
Get Salesforce Field Inspector running in under a minute.
Requirements
- Browser — Google Chrome or Microsoft Edge
- Salesforce — Lightning Experience enabled on your org
- Page type — Standard Lightning record pages (
/lightning/r/*/view)
- Permission — API Enabled on your Salesforce user profile
Installation
- Download or clone the repository
- Open Chrome or Edge and go to
chrome://extensions
- Enable Developer mode (toggle in the top-right corner)
- Click Load unpacked
- Select the
Salesforce-Field-Inspector folder
- Navigate to any Salesforce Lightning record page — the extension activates automatically
How to Use
- Open any Salesforce record page (Account, Contact, Opportunity, or any custom object)
- Hover over a field label or field value for ~0.8 seconds
- The metadata tooltip appears — move your mouse into it to keep it open
- Click Copy API Name to copy the field's API name to your clipboard
- Click Check FLS ↗ to open field-level security analysis in Salesforce Inspector
- Click ✕ or anywhere outside the tooltip to dismiss it
Check FLS Button
The Check FLS ↗ button requires one of the following extensions to be installed:
- Salesforce Inspector Advanced — takes priority if both are installed
- Salesforce Inspector Reloaded
Both are available on the Chrome Web Store. If neither is installed, clicking the button shows an installation prompt.
Troubleshooting
Tooltip does not appear
Confirm you are on a /lightning/r/ record page — not a list view, Setup page, or App Builder. Reload the Salesforce page after installing the extension.
"Session expired" error
Click ↺ Reload Page in the tooltip or manually refresh the Salesforce page. Sessions expire after the configured idle timeout (default 2 hours in Salesforce).
"Field not found" error
The field may be a compound field (Name, Address) or an internal system field. Hover directly over a sub-field (e.g. City or Street) rather than the compound wrapper.
"Check FLS ↗" shows an alert
Install Salesforce Inspector Advanced or Salesforce Inspector Reloaded from the Chrome Web Store and ensure it is enabled.
Features
A complete breakdown of everything Salesforce Field Inspector shows you.
Field Metadata Tooltip
Hover over any field label or value on a Lightning record page for 0.8 seconds and a tooltip appears with full field metadata. The tooltip stays open when you move your mouse into it.
📋
API Name
Highlighted in blue. Click Copy API Name to copy to clipboard with a ✓ confirmation.
🏷️
Label & Type
Display label and human-readable type — e.g. Formula (Text), Master-Detail, Multi-Select Picklist.
🔗
Lookup & Master-Detail
Referenced object, relationship API name, and cascade delete flag.
🧮
Formula
Full formula body in a scrollable code block — no need to open the field editor.
📦
Picklist Values
Up to 8 active values shown inline. +N more opens all values in Salesforce Setup.
🕒
History Tracked
Yes / No status fetched from the Salesforce Tooling API (EntityParticle).
✅
Access Flags
Required, Updateable, Createable, Unique, External ID, Encrypted.
🔒
Check FLS ↗
Opens Salesforce Inspector with a pre-built FieldPermissions SOQL to check profile and permission set access.
FLS SOQL
The Check FLS ↗ button pre-fills this query in Salesforce Inspector's Data Export tab:
SELECT Parent.Label, Parent.Profile.Name, Parent.IsOwnedByProfile, PermissionsRead, PermissionsEdit
FROM FieldPermissions
WHERE SobjectType = 'Account'
AND Field = 'Account.Industry'
ORDER BY Parent.IsOwnedByProfile DESC, Parent.Profile.Name
Parent.IsOwnedByProfile = true → Profile | false → Permission Set or Permission Set Group
All Supported Field Types
Text · Text Area · Long Text Area · Checkbox · Number · Currency · Percent · Date · Date/Time · Time · Email · Phone · URL · Picklist · Multi-Select Picklist · Lookup · Master-Detail · Formula · Auto Number · Record ID · Geolocation · Encrypted Text · File (Base64)
Performance
| Behaviour | Detail |
| Hover delay | 800 ms — tooltip only triggers after cursor stays on a field |
| Object metadata cache | 5 minutes per object — repeated hovers generate no extra API calls |
| History tracking cache | 5 minutes per field |
| Inspector detection cache | Lifetime of the page — checked once per page load |
Limitations
- Lightning Experience only — does not work on Classic, list views, Setup pages, Flow screens, or App Builder
- Compound fields — Name and Address compound wrappers are not resolved; hover over sub-fields (First Name, City, etc.)
- System fields — some internal fields may not resolve if they have no visible label in the DOM
- API access required — the running user must have API Enabled in their profile or permission set
Screenshots
Tooltip previews across different Salesforce field types.
Text Field
Formula Field
Lookup Field
Picklist Field
Currency Field
Master-Detail Field
Privacy Policy
Extension: Salesforce Field Inspector · Last updated: March 2026
Overview
Salesforce Field Inspector displays field schema metadata in a tooltip when you hover over fields on Salesforce Lightning record pages. This policy describes exactly what data the extension accesses, how it is used, and what it does not do.
Data We Access
Salesforce Session Cookie (sid)
Used solely as a Bearer token to authenticate calls to your own Salesforce org's REST and Tooling APIs. It is:
- Held in memory for the lifetime of the current page only
- Never written to disk,
localStorage, or any persistent storage
- Never transmitted to any server other than your own Salesforce org
- Discarded automatically when you navigate away or close the tab
Field Schema Metadata
Fetched from your own Salesforce org only. Schema-level only — no record data, no user data, no personal information is ever read. Cached in memory for 5 minutes and discarded on navigation.
Data We Do Not Access
- No record data — field values are never read
- No personal information — no names, emails, user IDs, or profile data
- No browsing history — scoped to Salesforce Lightning record pages only
- No clipboard reads — clipboard access is write-only (Copy API Name button)
Security Principles
🛡️Local Data Only
All data stays on your device. Nothing is sent to any external server.
🚫No Third-Party Sharing
Data is never shared with, sold to, or transmitted to any third party for any purpose.
📵No Data Collection
No personal or record data is collected, stored, or used.
⚖️No Legal Disclosures
No personal data is collected, so none can be shared for legal or compliance purposes.
🔐Privacy by Design
Only the minimum permissions strictly necessary to function are requested.
Permissions
| Permission | Why it is needed |
cookies | Reads the sid session cookie to authenticate REST API calls to your Salesforce org |
clipboardWrite | Powers the Copy API Name button — write-only, the extension never reads your clipboard |
management | Detects whether Salesforce Inspector is installed to enable the Check FLS button |
Host access to *.salesforce.com | Required to inject the content script and call the Salesforce REST/Tooling APIs |
Contact
For questions about this privacy policy, open an issue on the GitHub repository.
Disclaimer
🏢
No Affiliation with Salesforce
Salesforce Field Inspector is an independent, open-source project and is not affiliated with, endorsed by, sponsored by, or officially connected with Salesforce, Inc. in any way. "Salesforce" and related trademarks are the property of Salesforce, Inc.
⚠️
Provided As-Is
This extension is provided "as-is", without warranty of any kind, express or implied. The developer makes no guarantees regarding the accuracy, completeness, or reliability of the metadata displayed. All metadata is fetched directly from your own Salesforce org via Salesforce's public REST and Tooling APIs — the extension does not modify or interpret it.
⚖️
Limitation of Liability
In no event shall the developer be liable for any direct, indirect, incidental, special, or consequential damages arising from the use or inability to use this extension, including but not limited to API rate limit exhaustion, session expiry, loss of data, or decisions made based on metadata displayed.
👤
User Responsibility
Users are solely responsible for ensuring their use of this extension complies with their organisation's IT, security, and data governance policies. The extension accesses the Salesforce API using the user's own authenticated session — the developer has no access to, and no control over, the data in any user's Salesforce org.
🔌
Third-Party Extensions
The Check FLS feature relies on third-party Chrome extensions (Salesforce Inspector Advanced / Salesforce Inspector Reloaded) that are not affiliated with or controlled by this project. The developer is not responsible for the behaviour, availability, or data handling of those extensions.
🔓
Open Source — Fork & Use Freely
This project is open source and licensed under the
MIT License. You are free to fork, modify, and use this extension for your own purposes — personal or within your organisation — in accordance with the terms of that licence. Contributions and improvements via pull requests are welcome.