How We Test Digital Products

When we say a product was "tested by DigitalTools," this is the process we followed. We only use that phrase for products we have genuinely put through these steps.

What we test

  • Activation — does the key activate successfully on the official platform, on a real account, as described?
  • Delivery speed — how long does it actually take for the code or activation details to arrive after payment?
  • Compatibility — does the product work on the stated platform, edition and region?
  • Feature access — does the subscription or license unlock the features it advertises (for example, Canva Pro's Background Remover, or Microsoft 365's OneDrive storage)?
  • Longevity — does the license remain active over time, or does it lapse unexpectedly?

Our process

  1. Purchase or obtain the product through the same channel a customer would.
  2. Activate it on a clean, real account — not a vendor-provided demo account.
  3. Record the time from payment to working activation.
  4. Use the key features the product advertises and note anything that doesn't match.
  5. Re-check after a period to confirm the license stays active.

What we report

Where a product page or guide mentions testing, we describe what we actually observed: how delivery went, whether activation was smooth, and any limitations we hit. If a product has a restriction that matters — a region lock, a feature that's missing versus the vendor's full tier, or a renewal requirement — we state it plainly rather than bury it.

A note on scope

We cannot test every unit of every product — that isn't feasible for a marketplace. "Tested by DigitalTools" refers to representative sampling and the specific products named in our guides. Our Product Verification process, which applies to everything we sell, is separate and ongoing.

Related pages: Editorial Policy, Product Verification, and About DigitalTools.