Gamepad Tester

Gamepad Test

Frame Rate Test

Instantly measure your display's real-time FPS performance with our free online Frame Rate Test tool. No download, no sign-up required. The FPS Test tracks current FPS, average FPS, minimum FPS, maximum FPS, 1% lows, and frame time to help you evaluate your monitor's smoothness, browser rendering capability, and GPU performance.

Current FPS
0
frames/sec
Average
0
avg FPS
Minimum
0
min FPS
Maximum
0
max FPS
1% Low
0
stability
Real-Time FPS Graph 0s
Screen Resolution-
Viewport Size-
Device Pixel Ratio-
Color Depth-
Estimated Refresh Rate-
Frame Time-
Total Frames0
StatusIdle

What Is a Frame Rate Test?

A Frame Rate Test is a real-time diagnostic tool that measures how many frames per second (FPS) your browser, GPU, and display system can produce and render. Every second, your computer generates a series of still images that, when displayed rapidly in sequence, create the illusion of smooth motion. The number of those images displayed each second is your frame rate. Our FPS Test captures this value continuously and gives you a live readout of current FPS, average FPS, minimum FPS, maximum FPS, 1% low frames, and frame time.

Frame rate directly affects how fluid, responsive, and lifelike your visual experience feels. Whether you are gaming, editing video, or simply browsing, your FPS determines the difference between buttery-smooth motion and distracting choppiness. The Frame Rate Test on Gamepad Test gives you a precise, instant measurement without needing to install any third-party software.

This FPS Test works by using the browser's requestAnimationFrame API to count exactly how many frames your system renders in a given time window. It calculates FPS every 250 milliseconds and plots the values on a live graph so you can see not just your average performance but also any dips, stutters, or instability over time.

How the FPS Test Works: Step by Step

Understanding the process behind a Frame Rate Test helps you interpret your results correctly. Here is exactly how this FPS Test tool operates from the moment you click Start Test.

  • requestAnimationFrame loop: The tool registers a callback with the browser's built-in requestAnimationFrame API. The browser fires this callback once per display refresh cycle, synchronizing the measurement to your monitor's actual update rate.
  • Frame counting window: Each callback increments a frame counter. Every 250 milliseconds the tool calculates FPS by dividing the frame count by the elapsed time, then resets the counter for the next window.
  • Statistical aggregation: Each FPS sample is stored. The tool calculates the running minimum, maximum, and average across all samples. The 1% Low is computed by sorting all samples and averaging the bottom one percent, which reflects the worst stutters your system produces.
  • Frame time measurement: The gap between consecutive animation callbacks is recorded in milliseconds. This is your frame time. A frame time of 16.67 ms corresponds to 60 FPS. Lower is better.
  • Live graph rendering: Every new FPS sample is added to a rolling history and plotted as a line graph so you can see stability trends over the entire test duration.
  • Scene rendering: The canvas animation area draws moving objects that create a realistic GPU workload, ensuring the FPS measurement reflects actual rendering conditions rather than an idle browser.

How to Use This Frame Rate Test Tool

  • Click Start Test to begin the FPS measurement. The canvas animation will start and the counters will update in real time.
  • Watch the moving objects in the test canvas. These stress the GPU and browser renderer so the FPS reading reflects real-world load, not idle performance.
  • Monitor the statistics panel at the top of the page. Current FPS updates every 250 ms. Average, Minimum, Maximum, and 1% Low values accumulate over the full test duration.
  • Switch test modes using the tabs: Moving Rectangles, UFO Motion, Particle Stress, and GPU Rotation. Each mode stresses the renderer differently, helping you find which workload causes performance drops.
  • Adjust the controls to change speed, object size, opacity, and particle count. More particles and higher speeds create heavier GPU workloads and lower FPS on weaker systems.
  • Run the test for at least 20 to 30 seconds to collect enough samples for a reliable average FPS and 1% Low reading.
  • Use the FPS Cap selector to limit the test to a specific target frame rate such as 60 FPS or 144 FPS, useful for verifying that V-Sync or frame limiters are working correctly.
  • Click Export Results to download your FPS benchmark data as a JSON file for comparison across devices or sessions.

Understanding Your Frame Rate Test Results

The Frame Rate Test reports several distinct metrics. Knowing what each one means helps you diagnose performance issues accurately.

Current FPS

The FPS reading from the most recent 250 ms measurement window. This value fluctuates naturally; watch it over time rather than reacting to individual spikes.

Average FPS

The mean frame rate across the entire test session. This is the most reliable single number for comparing performance between devices or settings.

Minimum FPS

The single lowest FPS reading recorded. An unusually low minimum suggests a sudden spike in CPU or GPU usage causing a temporary freeze or hitch.

Maximum FPS

The highest FPS recorded. On uncapped tests this reveals your system's peak rendering capability for the given workload and browser configuration.

1% Low FPS

The average of the worst one percent of frames. This is the best indicator of perceived smoothness because it captures the stutters and hitches that feel most disruptive, even when average FPS looks healthy.

Frame Time

Time in milliseconds between consecutive frames. Consistent frame times feel smooth. Erratic frame times cause visible judder even at acceptable average FPS values.

Frame Rate Benchmarks: What Is a Good FPS?

Different use cases have different FPS requirements. The Frame Rate Test and FPS Test results below serve as a general benchmark guide to help you evaluate where your system stands.

Frame RateExperience LevelTypical Use CaseVerdict
Below 20 FPSUnplayableSeverely underpowered or throttled deviceNeeds troubleshooting
24 to 30 FPSCinematicFilm playback, casual browsingAcceptable for video
45 to 60 FPSSmoothEveryday use, single-player gamingGood
90 to 120 FPSVery smoothHigh-refresh gaming, VR, competitive titlesGreat
144 FPSEsports standard144 Hz monitors, FPS shooters, racing gamesExcellent
240 FPS+Professional level240 Hz+ displays, elite competitive gamingOutstanding

Frame Rate vs Refresh Rate: Key Differences

Frame rate and refresh rate are two separate concepts that work together. The Frame Rate Test measures FPS, which is controlled by your GPU and software. Refresh rate is measured in Hz and is a fixed hardware property of your monitor. For the best visual experience, your FPS should match or exceed your display's refresh rate.

When FPS is lower than your monitor's refresh rate, you lose frames and see incomplete motion updates. When FPS is higher, your GPU is producing frames faster than the screen can show them. Technologies like V-Sync, G-Sync (Nvidia), and FreeSync (AMD) bridge this gap by synchronizing the two values dynamically.

MetricWhat It MeasuresUnitControlled By
Frame Rate (FPS)Frames rendered per secondFPSGPU, CPU, browser, software settings
Refresh RateScreen updates per secondHzMonitor hardware
Frame TimeDuration of a single frame rendermsGPU and CPU workload
1% Low FPSAverage of worst 1% of framesFPSSystem stability and thermal management
Input LagDelay from input to screen responsemsFPS, display, and OS pipeline

Why Frame Rate Matters for Gaming and Video

For competitive gaming, the Frame Rate Test result directly correlates with your reaction time advantage and target clarity. A player running a 144 FPS game on a 144 Hz monitor sees game state updates 2.4 times more often than a player at 60 FPS. In fast-paced first-person shooters, battle royale titles, and fighting games, this translates into a tangible competitive edge.

For video creators and streamers, a stable FPS is essential for smooth recording and broadcast. Dropped frames during capture result in choppy footage and stuttering live streams. Running the FPS Test before a recording session helps confirm that your system can sustain the required frame rate without performance dips.

  • Reduced input lag: Higher FPS shortens the pipeline between your physical input and the resulting action on screen, making controls feel more immediate and precise.
  • Smoother motion: More frames per second means finer motion steps between each image, eliminating the choppy feel that lower frame rates produce.
  • Better target visibility: At higher FPS, fast-moving objects occupy more distinct positions per second, making them sharper and easier to track accurately.
  • Consistent frame delivery: Low 1% lows and consistent frame times prevent micro-stutters that break immersion and disrupt aim even when average FPS looks healthy.
  • VR comfort: Virtual reality headsets require sustained high FPS, typically 72 to 120 FPS minimum, to prevent motion sickness and maintain proper head-tracking synchronization.

What Affects Your FPS Test Results in a Browser?

Several factors influence the FPS you see during this Frame Rate Test. Understanding them helps you interpret your results in context and take targeted action if you need to improve performance.

  • Hardware acceleration: Whether your browser is using your GPU to accelerate canvas rendering has a major impact on FPS test results. Hardware acceleration must be enabled in your browser settings for optimal performance.
  • Browser engine differences: Chrome, Firefox, Edge, and Safari each use different JavaScript engines and canvas rendering paths. The same device can show meaningfully different FPS results across browsers.
  • Monitor refresh rate: The requestAnimationFrame API synchronizes to your display's refresh rate. On a 60 Hz monitor, the FPS cap is 60 even if your GPU could render faster. On a 144 Hz display, the ceiling rises accordingly.
  • CPU and GPU workload: Background processes, antivirus scans, software updates, and other open applications consume CPU and GPU resources, reducing the frames available for rendering.
  • Thermal throttling: Laptops and mobile devices reduce clock speeds when they overheat. Sustained heavy workloads trigger throttling, which causes FPS to drop progressively during the test.
  • Power plan settings: Laptops on battery-saving power plans artificially limit CPU and GPU performance. Switching to high-performance mode can significantly improve FPS test results.
  • Display scaling and DPI: High device pixel ratios (2x, 3x on Retina displays) mean the canvas renders more actual pixels, increasing GPU workload and reducing achievable FPS.

Tips to Improve Your Frame Rate

  • Enable hardware acceleration in your browser settings. In Chrome: Settings, System, toggle "Use hardware acceleration when available."
  • Close background tabs and applications that consume CPU, GPU, and RAM before running the FPS Test for the cleanest result.
  • Update your graphics drivers to the latest stable release from Nvidia, AMD, or Intel to ensure full GPU feature support and bug fixes.
  • Set your power plan to High Performance on Windows or disable "Low Power Mode" on macOS and mobile devices before testing.
  • Disable unnecessary browser extensions since some ad blockers and script injectors add rendering overhead that reduces FPS.
  • Lower your display scaling setting if you are testing on a high-DPI display and seeing unexpectedly low FPS numbers.
  • Keep your device cool by ensuring proper ventilation and avoiding testing on a soft surface that blocks airflow underneath a laptop.
  • Use a wired connection and avoid running heavy network tasks during the test if your system uses network-accelerated rendering pipelines.
  • Restart your browser before testing to clear memory leaks from long browsing sessions, which can degrade canvas rendering performance.

Test Modes Explained

The Frame Rate Test offers four canvas animation modes, each designed to stress your system differently. Switching between them during an FPS Test session gives a more complete picture of your rendering performance.

  • Moving Rectangles: Two filled rectangles travel horizontally across the canvas at different speeds. This is the lightest workload and closest to everyday browser UI rendering. A good baseline FPS starting point.
  • UFO Motion: Three UFO-shaped objects move at frame-rate-locked speeds simulating 30 FPS, 60 FPS, and uncapped motion simultaneously. This mode is excellent for visually comparing what different frame rates feel like side by side.
  • Particle Stress: Dozens to hundreds of bouncing particles fill the canvas. Increasing the particle count dramatically raises GPU workload, making this the best mode for stress testing rendering pipelines and finding the FPS ceiling of your system.
  • GPU Rotation: A set of rectangles rotates continuously using a canvas gradient, which exercises the GPU's fill rate and transformation pipeline. Useful for testing how well your system handles rotational and gradient-heavy render operations.

Frequently Asked Questions

A good result on the FPS Test depends on your monitor's refresh rate. If your display runs at 60 Hz, achieving a consistent 60 FPS is ideal. For 144 Hz monitors, you want sustained 144 FPS. In a browser context, reaching your monitor's native refresh rate with low frame time variance is the best possible outcome from the Frame Rate Test.
Games use direct GPU APIs like DirectX, Vulkan, or Metal that bypass browser overhead entirely. A browser-based Frame Rate Test operates through a JavaScript and canvas rendering layer, which adds CPU overhead and limits peak FPS. The FPS Test in a browser is an excellent benchmark for browser rendering performance but is not a direct comparison to native game FPS.
The 1% Low FPS is the average of the worst one percent of all frame rate samples recorded during your Frame Rate Test session. It is a more useful indicator of perceived smoothness than average FPS alone because it captures the brief but jarring dips that cause visible stutters. A high average FPS with a very low 1% Low FPS indicates an unstable or inconsistent rendering pipeline.
Yes. The Frame Rate Test works on iOS and Android browsers. Most modern smartphones run at 60 FPS or 90 FPS, with flagship devices reaching 120 FPS. Mobile results will typically be lower than desktop due to thermal constraints, smaller GPU resources, and power management systems that throttle performance to preserve battery life.
Several things can cap your Frame Rate Test result at 60 FPS. V-Sync enabled in your GPU control panel locks output to 60 FPS by default. Your browser may not be recognizing the monitor's high refresh rate, particularly if you have multiple displays connected and the browser window is on the non-primary screen. Check that hardware acceleration is enabled and try moving the browser window to your primary 144 Hz display.
FPS is a count of how many frames appear per second. Frame time is the duration in milliseconds that it takes to produce each individual frame. The two are mathematically related: frame time equals 1000 divided by FPS. A 60 FPS result means a frame time of roughly 16.67 ms. Frame time matters because two sessions can share the same average FPS but one can still feel smoother if its frame times are more consistent, meaning the gaps between frames are more uniform.
The Estimated Refresh Rate shown in the info panel is derived from your average FPS reading rather than directly queried from your operating system. It is an approximation based on what the requestAnimationFrame API actually delivers. For a confirmed hardware refresh rate value, check your operating system's display settings or GPU control panel.
Clicking Export Results downloads a JSON file containing all your Frame Rate Test statistics including current FPS, average FPS, minimum FPS, maximum FPS, total frames rendered, test duration, frame time, screen resolution, viewport size, device pixel ratio, and the browser's user agent string. This is useful for comparing performance across different browsers, devices, or settings over time.
Hardware acceleration is not strictly required, but it makes a significant difference. Without GPU acceleration, canvas rendering falls back to software CPU rendering, which produces much lower FPS. For accurate and meaningful Frame Rate Test results that reflect your GPU's actual capability, always ensure hardware acceleration is enabled in your browser before running the FPS Test.
Run the Frame Rate Test for a minimum of 20 to 30 seconds to collect enough FPS samples for statistically meaningful averages, minimums, and 1% Low values. A longer session of 60 seconds or more will also capture any thermal throttling effects on laptops, giving you a more realistic picture of sustained performance rather than just peak burst FPS.