Automattic/juice

Juice inlines CSS stylesheets into your HTML source.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on October 8th, 2011
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 233
Total Stargazers: 3,283 (+0)
Total Subscribers: 131 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 239.5 days
Mean response time: 741.8 days
90th percentile: 2369.2 days
Tracked items: 72

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Suggested Feature (11)
  • bug (3)
  • help wanted (3)
  • documentation (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Juice is a CSS inlining tool that embeds stylesheet rules directly into HTML elements as inline styles.

The tool solves the problem of CSS support limitations in email clients and other constrained HTML environments where external stylesheets or style tags are stripped or ignored. Juice parses HTML documents, extracts CSS rules from stylesheets, and applies them as inline style attributes on matching elements. This approach ensures styling is preserved even when the HTML is processed by systems that remove non-inline CSS.

Juice suits projects that need to generate styled HTML for email delivery, where external stylesheets are unreliable or unsupported. It works well for any workflow where HTML must be self-contained with all styling embedded. The tool is particularly valuable for email template generation and similar use cases where CSS inlining is a requirement rather than an optimization.

The project shows consistent maintenance with regular updates addressing bugs and edge cases. Development activity demonstrates responsiveness to reported issues and a willingness to refine the inlining behavior based on user feedback. The codebase receives incremental improvements rather than major architectural shifts, indicating a stable tool focused on reliability in its core function.