To test the standard global Redmi Note 13 with Selenium, configure ChromeDriver with the phone’s measured CSS viewport and device-pixel ratio—not its 2400 × 1080 physical display resolution. Xiaomi lists that panel resolution for the standard model, but it does not establish one universal browser viewport: measure the values on the target phone and browser, then use them in ChromeDriver’s mobile-emulation settings.
Which Redmi Note 13 are you testing?
This guide refers to the standard global Redmi Note 13, not the Redmi Note 13 5G, Pro, or Pro+ variants. Xiaomi lists a 2400 × 1080 display for the standard model; its support FAQ gives a 6.67-inch screen and 395 PPI. These are manufacturer specifications, not CSS viewport dimensions. Check the exact model and regional configuration you intend to support against Xiaomi’s product specifications.
As an Amazon Associate I earn from qualifying purchases.
A physical pixel is not the same as a CSS pixel. Chrome defines device-pixel ratio (DPR) as the ratio of physical screen pixels to CSS pixels. Entering 2400 × 1080 as the emulated CSS width and height would therefore assume a viewport that the panel specification alone does not establish.
Free tools Windows power users keep installed
One-click scans. No signup required.
Measure the phone’s effective browser viewport
Open the page on the target Redmi Note 13 in the Android browser you want to represent. Use that browser’s remote debugging console, or temporarily log the following from the page, to record the effective dimensions and DPR:
#1 Best Overall
- USA MARKET ONLY WORK ON TMOBILE MINT TELLO OR ANY UNDER TMOBILE NETWORK PHONE NEEDS A SIM CARD ALREADY ACTIVATED ,OUTSIDE USA WORKS ANY GSM CARRIER SIM GSM FCC ID: 2AFZZRN76L
- SIM1 + Hybrid* (SIM or MicroSD), supports dual 4G : 4G: 1/2/3/4/5/7/8/20/28/ 4G: LTE TDD: Band 38/40/41 3G: WCDMA: Band 2/4/5/8 2G: GSM: Quad Band.
- 6.67" AMOLED displayResolution: 2400 × 1080Refresh rate: Up to 120HzTouch sampling rate: 240HzBrightness: 1800nits peak brightnessBrightness: HBM 1200 nits (typ)Color depth: 8 bitContrast ratio: 5,000,000:1100% DCI- P3 wide color gamutPPI 394Corning Gorilla Glass 5Sunlight displayReading mode960Hz PWM dimming｜TÜV Rheinland Low Blue Light Certification (Hardware solution) | TÜV Rheinland Circadian Friendly Certification | TÜV Rheinland Flicker Free CertificationSGS Low Blue Light Certification
- Helio G99-Ultra6nm manufacturing process technologyCPU: Octa-core processor, up to 2.2GHzGPU: Mali-G57 MC2
- Proximity sensor | Ambient light sensor | Accelerometer | Electronic compass | IR blaster | Gyroscope / Bluetooth 5.3Wi-Fi Protocol: 802.11a/b/g/n/ac / Supports 2.4GHz Wi-Fi | 5GHz Wi-Fi Supports Wi-Fi Direct
console.log({
innerWidth: window.innerWidth,
innerHeight: window.innerHeight,
devicePixelRatio: window.devicePixelRatio,
screenWidth: window.screen.width,
screenHeight: window.screen.height
});Record the browser and version, Android software context, and orientation with the values. Repeat the measurement in portrait or landscape if both matter; the browser viewport can change with orientation and browser UI. Android’s guidance explains the role of the viewport in mobile layouts and recommends setting it to the device width: Targeting screens from web apps.
Configure Selenium ChromeDriver mobile emulation
ChromeDriver accepts custom mobile metrics through the mobileEmulation option and deviceMetrics. Use the CSS width, CSS height, and DPR measured on the target setup. The following Java example uses Selenium’s Chrome options and a map-based profile, following the shape of ChromeDriver’s mobile emulation documentation:
import java.util.HashMap;
import java.util.Map;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.chrome.ChromeOptions;
public class RedmiNote13MobileTest {
public static void main(String[] args) {
int measuredCssWidth = 393; // Replace with measured value
int measuredCssHeight = 873; // Replace with measured value
double measuredDpr = 2.75; // Replace with measured value
Map<String, Object> deviceMetrics = new HashMap<>();
deviceMetrics.put("width", measuredCssWidth);
deviceMetrics.put("height", measuredCssHeight);
deviceMetrics.put("pixelRatio", measuredDpr);
deviceMetrics.put("touch", true);
deviceMetrics.put("mobile", true);
Map<String, Object> mobileEmulation = new HashMap<>();
mobileEmulation.put("deviceMetrics", deviceMetrics);
ChromeOptions options = new ChromeOptions();
options.setExperimentalOption("mobileEmulation", mobileEmulation);
WebDriver driver = new ChromeDriver(options);
try {
driver.get("https://example.com");
// Add assertions for your site here.
} finally {
driver.quit();
}
}
}The values 393, 873, and 2.75 are illustrative placeholders, not claimed Redmi Note 13 measurements. Replace all three with values measured on your target phone and browser. Confirm the syntax against the installed Selenium and ChromeDriver versions. ChromeDriver also supports named device profiles where available, but custom measured metrics make the intended viewport explicit.
Verify the emulated viewport and responsive behavior
After opening your site, read back the browser’s effective values through Selenium’s JavaScript executor. Assert these against the profile you intended to configure; a mismatch can indicate that the emulation option was not applied or that the test is measuring a different context.
import org.openqa.selenium.JavascriptExecutor;
import java.util.Map;
JavascriptExecutor js = (JavascriptExecutor) driver;
Map<String, Object> viewport = (Map<String, Object>) js.executeScript(
"return {width: window.innerWidth, height: window.innerHeight, " +
"dpr: window.devicePixelRatio, screenWidth: window.screen.width, " +
"screenHeight: window.screen.height};"
);
System.out.println(viewport);Then test user-visible outcomes rather than treating a matching viewport as sufficient:
- Check that the page has no unintended horizontal overflow.
- Confirm important text, navigation, forms, and controls fit and remain usable at the target width.
- Exercise mobile navigation and other behavior triggered by your site’s responsive breakpoints.
- Run critical touch-oriented flows, such as opening menus and submitting forms.
Also test widths just above and below your own CSS breakpoints; one phone profile cannot cover every responsive transition. Chrome DevTools’ responsive mode can help inspect exact dimensions and media-query breakpoints. Its device mode is only an approximation, not a real handset run: Chrome DevTools says, “Think of device mode as a first-order approximation of how your page looks and feels on a mobile device.” See Chrome DevTools device mode.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Know what the Selenium result proves
Desktop-run ChromeDriver emulation is useful for repeatable automated layout checks, but it does not prove the page was tested on a Redmi Note 13. Chrome’s documentation notes that device mode does not actually run code on a mobile device and recommends testing on a real device when uncertain. Use a physical Redmi Note 13 for issues where actual touch input, browser integration, device-specific behavior, or performance matters.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors| Test mode | Useful for | What it does not establish |
|---|---|---|
| Selenium with ChromeDriver emulation | Repeatable viewport and mobile-metric checks in automation and CI. | Actual handset browser behavior, touch integration, or device performance. |
| Testing in a Redmi Note 13 browser | Checking real device, browser, and touch behavior. | Broad repeatability without access to the handset and a controlled test setup. |
Describe the first result precisely as “tested with Chrome mobile emulation configured to the measured Redmi Note 13 viewport,” rather than saying it was tested on the handset.
Troubleshooting common problems
The layout looks much wider than the phone
Check that you did not enter the panel’s 2400 × 1080 physical resolution as CSS dimensions. Re-measure window.innerWidth and window.innerHeight on the target browser, then use those CSS values in ChromeDriver.
The emulated dimensions or DPR do not match expectations
Log window.innerWidth, window.innerHeight, and window.devicePixelRatio after navigation. Verify the profile values, confirm ChromeDriver received the mobileEmulation option, and check that the phone measurement and Selenium run refer to the same orientation and intended browser context.
Mobile navigation or touch behavior still fails
Viewport emulation is not a substitute for real-device validation. Confirm that mobile and touch behavior are configured, test the relevant flow on the handset, and separately inspect whether the site’s own breakpoint or interaction code behaves as expected.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The test passes in emulation but fails on the phone
Keep both results: emulation provides a repeatable layout check, while the handset can reveal browser, touch, or performance differences. Reproduce the failure on the phone, record browser version and orientation, and adjust the automated test only if it can reliably represent the observed condition.
Or skip the browser setup
If you need a screenshot rather than a Selenium assertion, ScreenshotNeo takes a website capture through one GET request. For example, this cURL request saves a WebP screenshot of the target page:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo documentation for API details. ScreenshotNeo accepts cookie and consent banners before capture and removes 60+ known consent platforms, newsletter popups, and chat widgets; those steps can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits cost nothing, and response headers identify the page verdict and whether the request was billed. Its MCP server includes tools for AI agents to take screenshots. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000.
Sign up for 1,000 free screenshots a month—no card required.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Frequently Asked Questions
Does the standard Redmi Note 13 have a 2400 × 1080 screen?
Yes. Xiaomi lists that physical display resolution for the standard global Redmi Note 13; it is not the CSS viewport size to enter blindly in ChromeDriver.
Can ChromeDriver emulate the Redmi Note 13 exactly?
It can emulate configured mobile metrics, but that is not identical to running the page on the physical phone. Validate critical device-specific behavior on the handset.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
