SF Profiler

Salesforce debug log analyzer for Apex, Flow, and governor limits

SF Profiler helps Salesforce developers inspect large debug logs without sending log data to an external server. Open a log file in the browser and review the transaction timeline, slow operations, database activity, automation paths, and limit usage.

What SF Profiler analyzes

Salesforce debug logs can include Apex code, Flow interviews, workflow activity, validation and automation side effects, SOQL queries, DML operations, callouts, heap usage, CPU time, and governor limit samples. SF Profiler groups that activity into a readable profile with automation and insight views so a slow, recursive, or limit-heavy transaction is easier to understand.

Built for local log analysis

Log files are parsed on-device in the browser or desktop shell. That local-first approach is useful when a log contains production data, customer identifiers, org details, or other information that should not be uploaded just to troubleshoot performance.

Common troubleshooting paths

• Find slow Apex methods and nested execution paths.
• Trace Flow and workflow activity inside the same transaction.
• Compare repeated SOQL queries and DML operations.
• Review CPU time, heap, callout, future, queueable, and publish-immediate limits.