Perforce P4 Command Reference: Core CLI Commands, Workflow, and Examples

Perforce (Helix Core) has a broad command-line interface, and this guide is for engineers who need a fast, reliable command reference while working. It covers the core workflow, what key commands are used for, and a cleaned command list preserved from the original post.

Originally published on 2010-11-25; fully revised and updated.

This revision is based on the original post, Basic Perforce Command – P4 Command Reference, with improved structure and practical examples.

Perforce command workflow at a glance

This is the typical lifecycle for a basic P4 change: authenticate, sync, open files for change, resolve when needed, and submit.

flowchart TD
    A[Set P4PORT P4USER P4CLIENT] --> B[p4 login]
    B --> C[p4 sync]
    C --> D[Open files for add delete integrate]
    D --> E[p4 resolve]
    E --> F{Conflicts left}
    F -- yes --> E2[Resolve again]
    E2 --> F
    F -- no --> G[p4 submit]
    G --> H[Changelist stored in depot]

Quick start: connect and verify your workspace

Before editing or submitting, verify server connection, identity, and workspace context.

export P4PORT=perforce.example.com:1666
export P4USER=alice
export P4CLIENT=alice_ws

p4 login
p4 info
p4 clients
p4 sync //depot/main/...Code language: JavaScript (javascript)

Command comparison for everyday work

Use this quick comparison when deciding which command to run next.

Example: create and submit a basic changelist

This example shows a small add/delete change and submission through a numbered changelist.

p4 sync //depot/main/...

p4 add docs/release-notes.txt
p4 delete config/old.properties

p4 change
# Note the changelist number created in the editor

p4 submit -c 12345Code language: PHP (php)

Example: integrate and resolve

p4 integrate //depot/release/... //depot/main/...
p4 resolve
p4 submitCode language: JavaScript (javascript)

Basic P4 command reference

The table below preserves the original command coverage and descriptions, cleaned for readability.

Best practices and common pitfalls

• Run p4 info before major operations to confirm server, user, and workspace context.
• Use numbered changelists for anything non-trivial so you can track and review changes cleanly.
• Sync before integrate/resolve cycles to reduce avoidable conflicts.
• Use p4 have when troubleshooting version drift between local files and depot state.
• Treat admin-level commands (p4 admin, p4 verify, p4 triggers) as controlled operations.
• When uncertain about syntax on your server version, check p4 help <command>.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.