A PRACTICAL NEXT STEP

Compare your before and after captures

Record the conditions, import matching CSV captures, then inspect average FPS, slow frames and the timeline. Example data is explicitly synthetic.

Record your test conditions

Keep this record beside your raw captures. Repeat the same scene at least three times per setup; record unchanged or worse results too.

Read the test methodology

Your working checklist

Your settings and observations

Progress and notes stay in this browser. Capture files are not saved. Export a copy to keep your record.

FPS TEST

Check Your FPS. See the Full Picture.

REAL DATA. CLEAR INSIGHTS. HIGHER STANDARDS.

Choose test mode

Your files are processed in your browser. No file data is uploaded.

How do I capture a CSV?

Capture the same scene on Windows with PresentMon before and after your changes. Export each run as CSV. This webpage cannot read another application’s game FPS.

PresentMon capture documentation ↗

Requires Application, ProcessID, SwapChainAddress and MsBetweenPresents (case-insensitive), or CPUStartTime in milliseconds. CPUStartTime measures CPU cadence. Max 1,000,000 records and 256 streams per file.

Performance report

Your CSV dataChoose a baseline CSV, optionally add an after-changes capture, then analyze your files.

Your report starts here.

Choose a baseline CSV, optionally add an after-changes capture, then analyze your files.

Test conditions

Game: Not provided
Resolution: 2560 × 1440 (1440p)
Graphics preset: Not provided
Timing metric: Not provided
Valid duration: Not provided

View calculation method

Read what average FPS misses Recover from a worse result