Frequently asked questions

UICheck is a website QA tool for agencies, developers and designers. Paste a URL and it loads the page in real browsers at the screen sizes you pick, then reports layout, responsive, form and accessibility problems with screenshots and plain-language fixes.

No. Create a free account, paste a public URL and run the check in your browser. Everything runs on our servers.

Yes. UICheck tests the rendered page in a real browser, not your code, so it works with any platform or framework: WordPress, Next.js, React, Angular, Shopify, Webflow and plain HTML.

UICheck can open any public URL, including staging or preview links that don’t need a login. It can’t sign in to pages for you, and it never opens private or local network addresses such as localhost.

Accounts keep your checks and reports in one place, let you share them, and let us offer a free daily allowance fairly. If you start a check on the homepage before signing up, it starts by itself once your account is ready.

Sideways scrolling and content wider than the screen, uneven padding and misaligned blocks, text touching the screen edge, cut-off or tiny text, overlapping elements, tap targets that are too small or too close, form fields without labels, broken or never-loading images, JavaScript and network errors, and accessibility (WCAG) problems.

A single page usually takes under a minute for all screen sizes, and you can watch each one being tested live. Full-site checks take a few minutes; we email you when the report is ready.

Each screen size gets a score from 0 to 100 based on how many issues it has and how serious they are. The overall score averages the screen sizes, weighted toward the worst one, and maps to a grade from A+ to F. Any critical issue marks the check as failed.

Yes. Mark it “by design” and UICheck stops counting it on that page in future checks, at every screen size. Mark real problems “fixed” (one or many at once), or close their task in your tracker: UICheck checks the page again, confirms the fix or flags it as reopened, and emails you the result. On Lens and Prism that re-check starts right away; on Free, your next check of the page does it.

Some sites (often behind Cloudflare, Akamai or similar) block automated browsers. UICheck doesn’t try to get around that. Test a staging or preview URL instead, or ask the site owner to allow UICheck.

Mark it by design so it stops counting, and send the report link to ping@fulgid.in. We tune the checks against real sites, and every false alarm we fix becomes a permanent test.

Seven standard sizes: Small phone 360×800, Phone 390×844, Tablet 768×1024, Tablet landscape 1024×768, Laptop 1280×800, Desktop 1440×900 and Full HD 1920×1080. Paid plans can add custom sizes and 19 more devices such as iPhone SE, iPad Pro and a 4K TV.

Small phone, Phone, Tablet, Laptop and Desktop. Tablet landscape, Full HD, custom sizes and the extra devices are on Lens and Prism.

Every plan tests in Chrome. Lens and Prism also test in Safari (WebKit) and Firefox, which catches bugs that only show on iPhones and Macs.

Yes. Phone sizes run with mobile emulation and touch, so pages use their mobile layout and viewport settings as they would on a phone.

It reads your sitemap first, then follows links from your pages, staying on your own site. Lens checks up to 15 pages and Prism up to 50 in one check.

Yes. On Monitoring, add single pages, or switch on monitoring for a whole project (3 pages on Lens, 25 on Prism; a project uses one per page). Choose weekly or daily (Prism also every 6 hours). We email you, and post to Slack, only when something changed: text added, removed or reworded (shown as before → after), a screen that looks different, a watched word like “Sold out” that appeared or disappeared, or a problem that broke or got fixed. Each monitor has its own alert settings and sensitivity. Every screen size is checked weekly; checks in between use a phone and a desktop size. They don’t count against your daily checks.

No. A full-site check counts as one check, however many pages it covers.

Layouts often break between the standard sizes, for example only from 801 to 860px. On Lens and Prism, after the screen sizes are tested, UICheck widens the page from 320 to 1920px in 10px steps and shows exactly which widths scroll sideways, what sticks out, and a screenshot at the worst width.

In the app, open Figma in the left rail and click Connect with Figma, then approve read-only access. You can also paste a Figma personal access token with File content: read-only access.

Right-click a page frame in Figma and choose Copy link to selection. Each frame is compared at its own width, and you can add up to three frames (for example desktop, tablet and mobile) to one check.

The page and the design side by side, as an overlay and as a pixel difference, section by section. It also compares every design text with the page: font size, weight, typeface, colour and line height, plus texts missing from the page, typos and form fields.

The connected Figma account needs access to the file. Files from another team or organisation may also be blocked for Connect with Figma; in that case connect with a personal access token instead, which can read every file your account can open.

UICheck only asks for read-only access, stores it encrypted, and uses it only to read the frames you link. Disconnecting Figma deletes it.

On Prism, open Review on a check and switch from Screenshots to Live: the real site runs in up to four device frames at once. Click, scroll and type on any of them; with mirroring on, the same action happens on every screen. Going back to Screenshots keeps the session running.

Up to four screens per session and one session at a time. A session ends after 5 minutes without activity and lasts up to 20 minutes; you can start a new one any time.

A live session stays on the site you checked and its subdomains. Images and fonts from other domains still load, but going to another site is blocked. Run a new check to view a different site.

Yes. In Live, press Comment and click the spot: the frame on screen at that moment is saved with a pin, and the comment goes to the To fix list.

Yes: a PDF book with a chapter per screen size, or an Excel workbook with one row per issue, its screenshot, and columns to track status, owner and notes. On Free, your first report is complete and later ones leave out screenshots and minor issues; Lens and Prism are always complete.

Click Share on the report and make it public. Anyone with the link can view it without an account. Make it private again, or reset the link, at any time.

Yes. Issues marked fixed, by you or by closing their task in Linear, Jira, GitHub or Worksynk, are re-checked and confirmed or reopened, and issues marked by design stay muted, so each report shows what still needs work.

Yes, on every plan. Connect them in Integrations. Each finding then has a Create issue button that files it in Linear, Jira, GitHub or Worksynk with the fix, the screen sizes and a link to the report (Linear and Jira also get the screenshot with the problem outlined), and the Issues tab can send every critical finding at once. Slack gets report summaries and monitoring alerts.

A site you check again and again, saved with its pages, screen sizes, browser, staging login and page preparation (cookie banners, sliders, slow pages). Run project checks all of it in one click. Free has 1 project, Lens 10, Prism unlimited.

Yes, on Lens and Prism. When a project looks right, approve its screenshots as the baseline. Every later run compares each page and size pixel by pixel and shows the change side by side and as a diff, and you can approve the new look in one click. A project can also fail its quality gate on visual changes.

Every check passes or fails like a CI build: a re-scan fails when it finds new critical or major problems or the score drops; a first scan needs no critical problems and a score of at least 70. Re-scan from any report to see what improved.

Yes, on every plan. Create a CI token in Integrations, then add one step to GitHub Actions, GitLab CI or Bitbucket Pipelines (see Help → Check every deploy from CI). The build waits for the check, prints the result with a report link, and fails when the quality gate fails.

The Review tab of a check shows its pages in phone, tablet and desktop frames side by side. Links on the pages are clickable; a page that isn’t checked yet is checked when you open it and added to the same report (Free: one page, Lens: 15, Prism: 50). Problems are numbered on the page and hover looks show when you point at a button or link.

On Lens and Prism, press Comment (or C) in Review and click a spot, or drag a box. People reply, @mention each other and resolve it. The people involved get one grouped email, and Slack if it’s connected.

Yes. Invite them as a viewer (free on Prism). They get a simple view: the site on every device, their comments, and an Approve button for each page. They don’t see the technical report. You get an email when they approve.

One list of everything open on your sites: problems UICheck found on the latest check of each page, comments from Review and reports from the site widget. Each has a status, an assignee, a priority and can become an issue in Linear, Jira, GitHub or Worksynk. Closing the issue there resolves it here.

When a comment is resolved, or its task is closed in your tracker, UICheck checks that page again at the comment’s screen size. The comment then shows its spot before and now, and its writer gets an email to confirm with one click, or say it isn’t fixed.

A Feedback button on your own site, added with one script tag from the project page (Lens: one project, Prism: every project). Visitors mark up what they see and send it without an account (on Prism they can also record their screen for up to a minute). You also get their browser, screen size, console errors, failed requests and what they clicked in the minute before (never what they typed), plus answers to up to 5 questions of your own, and UICheck checks that page at their screen size.

Yes. On the project page set the button to Hidden: visitors don’t see it, and anyone who opens a page with ?uicheck=feedback at the end of the address (for example client.com/pricing?uicheck=feedback) gets the button for that browser tab. The project page gives you that link to copy. The widget also loads 8 seconds after the page, so it never affects page speed or SEO.

Yes. In Visual changes, choose Ignore areas and drag over a slider, a date or an ad: that part is never compared again for that page and width.

Yes, on Prism. A workspace holds your projects, checks, integrations and billing; invite people by email from Team. Prism includes 5 people, and each extra person is $10 a month. Free and Lens are for one person.

Owners do everything, including billing. Admins also manage people, integrations and CI tokens. Members run checks, work on projects, triage findings and create issues, and delete only their own checks. Viewers can look at projects and reports but change nothing.

Yes. Invite them as viewers: up to 10 per workspace on Prism, free, read-only. For one report, a public share link works on every plan.

Yes. Team shows an activity log: checks run, projects changed, monitoring, findings marked, issues created, people invited and removed, and settings changed.

Yes. Switch between them from the top of the app’s side bar. Each workspace has its own plan; on Prism you can create more, for example one per client.

Free: 5 checks a day on 5 screen sizes. Lens ($5 a month): 20 checks a day, every screen size, Safari and Firefox, full-site checks up to 15 pages, the breakpoint sweep and Figma comparison. Prism ($50 a month): unlimited checks, up to 50 pages per full-site check, the live site view, white-label reports and a team of 5 ($10 a month for each extra person).

At midnight UTC every day.

Paid plans are monthly subscriptions billed by Dodo Payments, which accepts cards and many local payment methods and handles taxes and invoices.

In the app, open Billing and choose Cancel subscription. You keep your plan until the end of the month you paid for, then move to Free. Your checks and reports stay.

Yes: a full refund if you ask within 7 days of first paying for a plan. Renewals aren’t refunded, and billing mistakes always are. See the Refund & Cancellation Policy for details.

In the app under Billing, with a PDF for each payment. You can also update your card there.

Enter your email and we send you a 6-digit code; no password needed. If you prefer, choose Use a password instead, or set a password later in Account.

It can take a minute; check spam and promotions. Codes expire after 10 minutes and work once. You can resend a code after 30 seconds, or sign in with your password if you set one.

In the app, open Account and choose Delete my account. This cancels any subscription and permanently deletes your checks, screenshots, reports and Figma connection.

No need: on Prism, invite each person into your workspace so everyone has their own sign-in and the activity log shows who did what. On every plan you can share single reports with a public link or as PDF and Excel.

Yes. In Account, Your data downloads one file with everything UICheck stores about you: profile, workspaces, the checks you started with every finding, projects, monitors and what you marked or created. Passwords, tokens and keys are never included.

Your name and email, the URLs you check, screenshots and results, and billing status from Dodo Payments. Passwords and sign-in codes are stored only as hashes, and Figma access is encrypted. The Privacy Policy has the full list.

Only the people in your workspace, unless you make a report public. Screenshots are served through short-lived links checked against your account or the report’s share link.

No. Your pages, screenshots and reports are used only to run UICheck for you.