Local · Private · Standalone

See exactly what happened in a Salesforce deployment.

Load the JSON output from sf project deploy report and inspect every lifecycle step, error, component, test, file, option, and raw field.

Drop a deployment report here

or choose the JSON file from your computer

Choose JSON report

Your report never leaves this browser.

Help & setup

From Salesforce to a readable deployment report.

Salesforce CLI is a small, official Salesforce program that runs commands on your computer. Follow these steps once to connect it, then use two commands whenever you need a report.

Use your Salesforce org in these commands

Set these once and every command below will update for you.

Org name / CLI alias A short name you choose, such as block-uat. The login command creates this alias. Instance URL Use the Salesforce My Domain login URL for the exact sandbox or org—not a Lightning page URL.

Get a deployment report

Start with the exact Salesforce org that contains the deployment. In Salesforce, an “org” means one Salesforce environment, such as a sandbox or production.

Install Salesforce CLI

Download the installer for macOS, Windows, or Linux from the official Salesforce CLI page, run it, then close and reopen your terminal.

On macOS, open Terminal. On Windows, open PowerShell. Confirm the installation:
Check the installation
```
sf --version
```
Confirm which Salesforce org to use

Ask your Salesforce administrator or release owner for the org’s login URL and whether it is a sandbox or production. Enter the URL and a short name in the fields above.

Be deliberate here: do not authenticate to production unless the report you need is actually in production and you are authorized to access it.
Sign in through your browser

The command below uses the org values saved at the top. If it still contains capitalized placeholders, fill in those settings before running it.
Connect a sandbox
```
sf org login web --alias my-sandbox --instance-url https://YOUR_DOMAIN--YOUR_SANDBOX.sandbox.my.salesforce.com
```
A browser window opens. Complete your normal Salesforce or SSO sign-in, approve access if asked, and return to the terminal. For a production org, the URL normally ends in .my.salesforce.com instead.
Verify the connection

List the orgs currently connected to Salesforce CLI and confirm that the org name you chose appears:
List connected orgs
```
sf org list
```
Find the deployment ID

If you already see the deployment summary in Salesforce, you can get its ID directly from Setup:
Find the ID in Salesforce Setup

⚙ Setup→Quick Find: Deployment Status→Deployment Status
1. Find the deployment or validation under In Progress, Pending, Failed, or Succeeded. Use the status, start time, and deployed-by name to identify the right one.
2. Click View Details next to it.
3. In the browser address bar, find asyncId=0Af…. Copy only the value beginning with 0Af, stopping before the next & if there is one.
Setup can display deployments from the last 30 days, but sf project deploy report accepts a deployment ID for 10 days. Choose a recent deployment for this viewer.

Or use this Tooling API query to list the last 10 days from the terminal. A value of true under CheckOnly means the job was a validation rather than an actual deployment.
List recent deployment IDs
```
sf data query --use-tooling-api --target-org my-sandbox --query "SELECT Id, Status, CreatedDate, CheckOnly, NumberComponentsTotal, NumberComponentErrors, NumberTestsTotal, NumberTestErrors FROM DeployRequest WHERE CreatedDate = LAST_N_DAYS:10 ORDER BY CreatedDate DESC" --result-format human
```
Create the JSON file

Paste the 0Af… ID below. The command updates automatically. Copy it into the terminal to ask Salesforce for the complete Metadata API report and save it as deployment-report.json in the folder shown by your terminal.
Deployment ID
Download this deployment report
```
sf project deploy report --job-id 0AfPASTE_DEPLOYMENT_ID_HERE --target-org my-sandbox --json > deployment-report.json
```
Open it here

Return to this page, choose Open JSON, and select deployment-report.json. You can also drag the file onto the viewer. The file is read locally and is never uploaded.

What talks to what?

The commands use Salesforce APIs on your behalf. This page does not connect to Salesforce at all.

Browser sign-in and OAuth

sf org login web opens Salesforce’s sign-in page and authorizes the CLI. Your password and access token are not placed in the JSON report or given to this viewer.

Tooling API

sf data query --use-tooling-api queries DeployRequest so you can find recent job IDs and their high-level status.

Metadata API

sf project deploy report requests the detailed result for one deployment or validation: components, errors, tests, coverage, timing, and other recorded fields.

This local viewer

The browser reads the JSON file you select, renders it, and keeps it in this page’s memory. It makes no Salesforce API request and uploads nothing.

For more detail, see Salesforce’s official references for browser login, data query, and deployment reports.