How to Check What Your Website Looks Like on Mobile
Over 60% of global web traffic comes from mobile devices. If your website doesn’t look right on a phone, you’re losing more than half your visitors. Here’s how to check.
Why You Can’t Trust Your Desktop Browser Alone
When you build and test on a desktop, you’re seeing the site at one specific viewport width - probably somewhere between 1200px and 1920px. The mobile experience is a completely different layout, often with different font sizes, different element ordering, and different interaction patterns.
The only way to verify the mobile experience is to actually render it at mobile dimensions. You have several options.
Method 1: Chrome DevTools Device Mode
The fastest method that requires no extra setup.
- Open Chrome and navigate to your site
- Press
F12to open DevTools (or right-click → Inspect) - Click the device toolbar icon - it looks like a phone and tablet
- Select a preset device from the dropdown, or enter custom dimensions
- Reload the page
This renders the page at the specified dimensions and with touch events enabled. It’s excellent for debugging layout issues during development.
Limitation: It’s browser-based emulation, not a real device. Some things behave differently - particularly touch scrolling, input handling, and how certain CSS properties render.
Method 2: Firefox Responsive Design Mode
Firefox has its own responsive testing mode:
- Press
F12and click the responsive design icon - Or use
Ctrl + Shift + M
Firefox’s implementation is slightly different from Chrome’s and can sometimes catch issues that Chrome’s emulation misses, particularly with CSS grid and flexbox edge cases.
Method 3: Real Device Testing
Testing on an actual iPhone or Android device is the gold standard. It’s the only way to see exactly how your CSS, fonts, and interactions feel to a real user.
How to test on a real device during development:
- Serve your local site on your network IP instead of localhost (most dev servers support
--host) - Connect your phone to the same WiFi
- Navigate to
http://[your-machine-ip]:[port]from your phone’s browser
This requires being on the same network, but there’s no substitute for real-device testing for anything you’re about to ship.
Method 4: Remote Debugging
If you need to inspect element behavior on an actual mobile device:
- Android + Chrome: Enable USB debugging in Developer Options, connect via USB, then use
chrome://inspecton your desktop - iOS + Safari: Enable Web Inspector in Safari settings on your iPhone, then connect via USB and use Safari’s Develop menu on your Mac
This lets you use full desktop DevTools while the browser runs on the physical device.
Method 5: MockupSnap
If you need a professional screenshot of how your site looks on mobile - not for debugging, but for presentation, documentation, or review - MockupSnap is the fastest option.
Paste your URL and MockupSnap’s cloud renderer visits the page in a real headless Chromium browser at iPhone 15 Pro dimensions (393×852px), captures a full-resolution screenshot, and composites it inside a device frame.
The result is a publication-ready mobile screenshot in about 60 seconds, alongside iPad Air, MacBook Pro, and Desktop 1080p screenshots captured in the same session.
This is useful when:
- You need visual proof of mobile compatibility for a client or stakeholder
- You’re writing documentation and need consistent, professional screenshots
- You want to show mobile/desktop side-by-side in a presentation
Which Method Should You Use?
| Situation | Best method |
|---|---|
| Debugging layout during development | Chrome DevTools |
| Cross-browser CSS differences | Firefox DevTools |
| Final QA before launch | Real device |
| Presentation or documentation screenshot | MockupSnap |
| Advanced debugging on real hardware | Remote debugging |
Common Mobile Layout Issues to Check
Once you can preview the mobile view, here’s what to look for:
Text size: Is body text at least 16px? Smaller text requires pinch-to-zoom, which frustrates users.
Touch targets: Are buttons and links at least 44×44px? The minimum recommended touch target size per Apple’s HIG and Google’s Material Design guidelines.
Horizontal scrolling: Does anything overflow horizontally? Fixed-width elements (especially images and tables) commonly break mobile layouts.
Navigation: Is the mobile nav accessible and functional? Hamburger menus that work on desktop sometimes fail to open on mobile.
Images: Are images responsive? max-width: 100% on images is the most basic responsive image technique.
Forms: Do form fields zoom on focus? iOS Safari zooms into inputs smaller than 16px by default.
Summary
For development, Chrome DevTools is your first line of defense. For production QA, test on real devices. For anything you need to communicate to others - MockupSnap turns your URL into professional device screenshots instantly, without requiring any device at all.