Share CSS without losing the cascade
CSS bugs are order bugs. The rule that wins is the one that comes last, has the higher specificity, or carries !important — and every one of those details disappears the moment a stylesheet is pasted into a chat window that reflows it.
Keep the order and the comments
Paste the stylesheet as-is, with comments. A comment like /* overrides bootstrap */ is often the explanation for the bug. Choose CSS as the language so selectors, properties and values are distinguishable.
The kind of detail worth preserving
/* specificity: 0,2,0 — beats .card .title below */
.panel .title { color: #0f172a; }
.card .title { color: #64748b; }What to strip
- Customer-specific selectors that reveal names or plan tiers.
- Absolute asset URLs pointing at internal buckets or signed CDN links.
- A/B test classes that expose experiment names.
- Fonts and images — a paste is text; the reader does not need your assets.
Sharing the computed value instead
Sometimes the stylesheet is not the problem: the problem is what the browser computed. Paste the relevant rules from devtools, or the output of a small script, rather than screenshots of the styles panel. Text can be searched and diffed; a screenshot of a styles panel cannot.
Frequently asked questions
Does the paste apply my CSS?
No. The stylesheet is displayed as text and never injected into the page, so it cannot affect the site or the reader.
Can I share a whole framework stylesheet?
Up to 100,000 characters. A minified framework file usually exceeds that — share the specific rules involved instead.
Is SCSS or LESS supported?
The highlighting is CSS-based; SCSS and LESS mostly colour correctly because they share syntax. Nested selectors may look slightly off.
Can I password-protect a stylesheet?
Yes, and for client work it is worth doing. Send the password separately from the link.