Testing · head to head
Percy vs Zimpler

Percy
Testing
Visual regression testing owned by BrowserStack, with a permanent free tier for low screenshot volume
- From
- Free
- Free plan
- Yes

Zimpler
APIs
Nordic and Brazilian account-to-account payments for regulated high-risk sectors
- From
- On request
- Free plan
- No
The short version
- Percy is free; Zimpler prices on request.
- Only Percy lists screenshot diffing; only Zimpler lists bank payments.
- Where Percy falls short: paid tier pricing above the free tier is not transparently published as a fixed number, requiring a quote to know actual cost at scale.
- Prices and features on this page were last checked on 20 November 2026.
How do Percy and Zimpler differ?
Percy and Zimpler differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Percy and Zimpler actually diverge.
Which features does each one have?
They share no listed features; 6 appear only for Percy and 6 only for Zimpler. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Percy
- Screenshot diffing
- Framework integrations
- Responsive and cross-browser snapshots
- Review workflow
- Build history
- BrowserStack platform integration
Only in Zimpler
- Bank payments
- BankID identity
- Payouts
- Recurring payments
- Risk screening
- Brazil coverage
What is each one used for?
Zimpler is most often brought in for A Nordic merchant wanting instant bank payouts rather than card refunds. The jobs each tool is most often brought in to do.
Percy
- A team already on BrowserStack for device testing that wants to add visual regression without a separate vendor relationshipnot Zimpler
- A low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anythingnot Zimpler
- A team wanting a lower cost per screenshot than Applitools and willing to tolerate more manual false-positive triagenot Zimpler
- A Cypress or Playwright test suite adding visual checks without changing its existing test runnernot Zimpler
Zimpler
- A Swedish gambling operator needing deposit and verified identity in a single customer flownot Percy
- A Nordic merchant wanting instant bank payouts rather than card refundsnot Percy
- A trading platform where confirming account ownership before funding is a regulatory requirementnot Percy
- A European operator expanding into Brazil and wanting one provider across both marketsnot Percy
Where do Percy and Zimpler fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Percy
- Pixel-based diffing generates more false positives from font rendering and anti-aliasing noise than Applitools' AI-based comparison, which trains some teams to start ignoring diff alerts over time
- It is billed separately from core BrowserStack device testing, and stacking Percy with other BrowserStack modules such as Accessibility Testing materially increases total contract value beyond the headline device testing price
- Paid tier pricing above the free tier is not transparently published as a fixed number, requiring a quote to know actual cost at scale
- The free tier's 5,000-screenshot cap is easy to exceed for any team running visual tests across multiple browsers and viewports on every commit, pushing many active projects into a paid tier faster than the free number suggests
- As part of a larger acquired portfolio, Percy's roadmap priority within BrowserStack's broader product strategy is less certain than it would be as a standalone company's sole focus
Zimpler
- Pricing is not published and is set by industry and risk profile, so smaller merchants cannot benchmark a quote and often discover they are paying well above a general-purpose provider
- As a payment facilitator carrying merchant risk, it declines or offboards merchants on risk grounds, which makes it a dependency you cannot assume will persist
- Its strength is concentrated in the Nordics, and coverage in southern and eastern Europe is thinner than pan-European account-to-account specialists
- Revenue concentration in iGaming ties the provider to a sector under constant regulatory change, so licence changes in one market affect the supplier as well as the merchant
- Bank transfers have no chargeback protection, so disputes are handled commercially and consumers used to card protections may resist the payment method
How much do Percy and Zimpler cost?
Percy is free to use; Zimpler is priced on request. Plan by plan below, from each vendor's own pricing page.
Percy
Free- FreeFree
- 5,000 screenshots a month
- Unlimited users and projects
- 30-day build history
- PercyOn request
- Priced by screenshot volume above the free tier
- Sold separately from core BrowserStack device testing plans
- Get a current quote before assuming bundled pricing with other BrowserStack products
Zimpler
On request- Zimpler paymentsOn request
- Per-transaction pricing quoted by industry, risk and volume
- Separate pricing for payouts and identity verification
- Merchant underwriting required, with sector restrictions
Which should you pick?
Choose Percy if
- You need screenshot diffing.
- You want to start without paying.
- You also want framework integrations.
Choose Zimpler if
- You need bank payments.
- You work on Web, API.
- You also want bankid identity.
Questions people ask
- Is Percy or Zimpler better?
- Neither clearly leads. Percy starts at Free and Zimpler at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Percy or Zimpler?
- Percy has a free tier; the other does not. Paid plans start at Free for Percy and On request for Zimpler.
- Does Percy or Zimpler run on more platforms?
- Percy runs on Web. Zimpler runs on Web, API.
- Can I use Percy for free?
- Yes. Percy has a free tier, so you can try it without paying. Zimpler starts at On request.
- What is Percy best used for?
- Percy is most often used for a team already on browserstack for device testing that wants to add visual regression without a separate vendor relationship, a low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anything, a team wanting a lower cost per screenshot than applitools and willing to tolerate more manual false-positive triage, a cypress or playwright test suite adding visual checks without changing its existing test runner. Of those, a team already on browserstack for device testing that wants to add visual regression without a separate vendor relationship and a low-traffic project that can run indefinitely on the 5,000-screenshot free tier without paying anything are not what Zimpler is typically brought in for.
- What can Percy do that Zimpler cannot?
- Percy covers Screenshot diffing, Framework integrations, Responsive and cross-browser snapshots, Review workflow. Zimpler covers Bank payments, BankID identity, Payouts, Recurring payments.
Answered from the vendors’ own pages
Percy: Is Percy free?
Yes for up to 5,000 screenshots a month with unlimited users and projects; beyond that it is a paid, quote-priced module.
Zimpler: Which markets does Zimpler cover?
Sweden and the Nordics primarily, plus the wider EU and Brazil. It is strongest where national electronic identity schemes exist.
Percy: Is Percy included if I already pay for BrowserStack device testing?
No, it is billed separately by screenshot volume, not bundled into core device testing plans.
Zimpler: Does it handle identity verification?
Yes. In the Nordics it captures BankID identity alongside the payment, which removes a separate verification step.
Percy: How does it compare to Applitools?
Percy uses pixel-based diffing, which is generally cheaper per screenshot but produces more false positives than Applitools' AI-based perceptual comparison.
Zimpler: Is pricing published?
No. It is quoted per merchant based on sector, risk and volume, and merchants must pass underwriting first.
Related pages
Other head to heads
- Percy vs Applitools
- Percy vs Sauce Labs
- Percy vs BrowserStack
- Percy vs Playwright
- Percy vs Cypress
- Percy vs TestRail
- Percy vs Katalon
- Percy vs PractiTest
- Percy vs Jest
- Percy vs Xray Test Management
- Percy vs JUnit
- Percy vs Puppeteer
- Percy vs Kameleoon
- Percy vs Qase
- Percy vs Robot Framework
- Percy vs Zephyr Scale
- Percy vs Ranorex
- Percy vs Appium
- Percy vs Trustly
- Percy vs Volt
- Percy vs Brite Payments
- Percy vs TrueLayer
- Percy vs Token.io
- Percy vs Neonomics
- Percy vs Tink
- Percy vs Yapily
- Percy vs Dwolla
- Percy vs Sila
- Percy vs Fintecture
- Percy vs Moov
- Percy vs Janus Gateway
- Percy vs Method Financial
- Percy vs Sensedia
- Percy vs Spring Cloud Gateway
- Percy vs TIBCO Mashery
- Percy vs Kong Gateway
- Zimpler vs Applitools
- Zimpler vs Sauce Labs
- Zimpler vs BrowserStack
- Zimpler vs Playwright
- Zimpler vs Cypress
- Zimpler vs TestRail
- Zimpler vs Katalon
- Zimpler vs PractiTest
- Zimpler vs Jest
- Zimpler vs Xray Test Management
- Zimpler vs JUnit
- Zimpler vs Puppeteer
- Zimpler vs Kameleoon
- Zimpler vs Qase
- Zimpler vs Robot Framework
- Zimpler vs Zephyr Scale
- Zimpler vs Ranorex
- Zimpler vs Appium
- Zimpler vs Trustly
- Zimpler vs Volt
- Zimpler vs Brite Payments
- Zimpler vs TrueLayer
- Zimpler vs Token.io
- Zimpler vs Neonomics
- Zimpler vs Tink
- Zimpler vs Yapily
- Zimpler vs Dwolla
- Zimpler vs Sila
- Zimpler vs Fintecture
- Zimpler vs Moov
- Zimpler vs Janus Gateway
- Zimpler vs Method Financial
- Zimpler vs Sensedia
- Zimpler vs Spring Cloud Gateway
- Zimpler vs TIBCO Mashery
- Zimpler vs Kong Gateway
