How it works
What it captures
Compare
Pricing
Blog
Join the waitlist
Skip to content
Loupely Lens
About
Acceptable Use Policy
Auth-Callback
Blog
Changelog
Loupely Lens
Toggle Menu
All Categories
Account & Plans
Getting Started
Legal Reference
Loupely Lens
Security & Privacy
Troubleshooting
Popular Search
chrome
View Categories
Home
Knowledge Base
how-it-works
how-it-works
The Full CSS Cascade: What Lens Captures
What the Browser Knows vs. What You Can Read
Competitor Element Detection
Glossary: CSS Specificity and the Cascade
Color Conflict
Layout Constraint
Overlap and Z-Index Conflicts
Visibility Hidden
Spacing, Margin, and Padding Issues
Triage Routes for Lens
Automatic Problem Detection
Origin Classification: Where Each Rule Came From
The Override Prescription: What It Is and When You Get One
Reading the CSS Origin Label on Your Capture
Losing Rules Detection: Why Your Change Isn’t Taking Effect
Ancestor Traversal: Why the Problem Often Isn’t on the Element
The ‘Anything Else?’ Field: When to Use It and Why
Loupely Lens Data Handling
How to Use the Computed Styles Panel
How the CSS Rule Engine Works
Account Security and Sign-In
Annual Plans: What’s Included and How They Work
The Lens Diagnosis Popup: Anatomy
The Lens Capture File
The Triage Page: What It Shows and How to Use It
Understanding the Fight View
Live Preview: What It Is and What It Means
What Is Loupely Lens
Lens on Non-WordPress Sites
About
Acceptable Use Policy
Auth-Callback
Blog
Changelog