by Simon Mista 0 (0 reviews)

Theme SCSS Compiler

Name: Theme SCSS Compiler
Author: Simon Mista

Compile SCSS to CSS in the WordPress admin. No Node.js, no npm, no build step. Several file pairs, per-file cache busting, rebuild on change.

Theme SCSS Compiler ranks #16,141 among WordPress.org plugins with 100+ active installations, is #1,116 of 4,943 in the Utilities & Tools category, and was last updated Aug 22, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v1.0.8 Current Version v1.0.8

Updated 3 weeks ago Last Update on 22 Aug, 2026

Refreshed 8 hours ago Last Refreshed on

#1,116 of 4,943 in Utilities & Tools Top 25% by installs Actively maintained

View on WordPress.org

Rank

#16,141

— No change

Active Installs

100+

-16%

KW Avg Position

— No change

Downloads

896

+4 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 200

Total Progress 25%

100+ 200+

3,182

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 75 more installs to reach 200+

Rank Changes

Current #16,141

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for Theme SCSS Compiler. Checked 1 month ago.

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.0.8
Last Updated: Aug 22, 2026
Requires WP: 6.3+
Tested Up To: 7.1
PHP Version: 8.1 or higher
Author: Simon Mista

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

compiler css sass scss theme

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,756

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,007

Elementor Website Builder – more than just a page builder

10M+ installs

Contact Form 7

10M+ installs

All-in-One WP Migration and Backup

5M+ installs

#10

UpdraftPlus: WP Backup & Migration Plugin

3M+ installs

#15

WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager

View all Utilities-and-tools plugins

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress theme developers who want to compile SCSS/Sass to CSS without Node.js or build tools. It handles multiple SCSS-to-CSS file pairs directly in the WP admin, with automatic recompilation and cache-busting versioning when source files or their imports change.

Multiple SCSS to CSS file pairs
Per-pair frontend or admin context
Per-file automatic version bumping
Smart change detection
@import-aware auto-recompile
Compressed or expanded output
Auto-compile on source change
Concurrent-compile lock

Frequently Asked Questions

Common questions about Theme SCSS Compiler

The plugin bundles scssphp 2.1, which supports modern SCSS syntax compatible with Dart Sass.

Only when the compiled CSS output for that specific pair has changed compared to the previously written file. Comments-only edits or no-op SCSS changes that result in identical compressed CSS do not bust the cache. Other pairs keep their existing versions.

Each pair has a Context field. Pairs set to Frontend are auto-enqueued via wp_enqueue_scripts (only on the public site). Pairs set to Admin are auto-enqueued via admin_enqueue_scripts (only on /wp-admin pages). The style_loader_src version filter applies in both contexts whenever a configured CSS file is printed. Default for new pairs is Frontend.

By default only WordPress administrators (users with the manage_options capability). The Tools → Theme SCSS Compiler submenu, the form save handler, the AJAX compile endpoint and the auto-compile hook all enforce this capability. Editors, Authors and other roles cannot see or use the plugin's UI. If you need to grant access to a different role (for example a custom "Theme Developer" role), use the tscsscompiler_capability filter: add_filter( 'tscsscompiler_capability', static function () { return 'edit_theme_options'; } );

If Auto-compile is enabled (default: on), every admin page load checks whether the configured CSS files exist or whether the SCSS source — or any of its @import-ed partials — is newer. Missing or stale outputs are compiled silently. This protects against white layouts after a fresh deployment or git pull.

Yes. After every successful compile the plugin records the full list of files that scssphp pulled in (including transitive @import / @use / @forward chains) into a per-pair dependency map. The auto-compile check compares the modification time of each tracked partial against the CSS output. So if style.scss does @import "menu-styles"; and you edit menu-styles.scss, the next admin page load triggers a recompile automatically — you don't have to touch style.scss.

Both work. Auto-enqueue is on by default — the plugin runs wp_enqueue_style() for every configured pair on its respective context (Frontend or Admin). It runs at PHP_INT_MAX priority and skips any URL that's already registered, so it never duplicates output. If you'd rather keep full control of the asset pipeline in your theme, just disable the option and call wp_enqueue_style() yourself.

Yes. Define TSCSSCOMPILER_PAIRS and the plugin reads pairs from there instead of the database. The admin form switches to a read-only state and the save handler is disabled. define( 'TSCSSCOMPILER_PAIRS', [ [ 'scss_path' => 'assets/scss/style.scss', 'css_path' => 'assets/css/style.css', 'version' => '1.0.0', 'context' => 'frontend' ], [ 'scss_path' => 'assets/scss/style-admin.scss', 'css_path' => 'assets/css/style-admin.css', 'version' => '1.0.0', 'context' => 'admin' ], ] ); The remaining behaviours can be toggled individually: TSCSSCOMPILER_AUTO_COMPILE – true / false TSCSSCOMPILER_BUMP_VERSION – true / false (note: bumping is a no-op when defined via constant — versions live in your code) TSCSSCOMPILER_AUTO_ENQUEUE – true / false TSCSSCOMPILER_OUTPUT_STYLE – 'compressed' / 'expanded'

Three common places: 1. wp-config.php (loaded earliest, recommended for everything): define( 'TSCSSCOMPILER_OUTPUT_STYLE', 'compressed' ); 2. Theme functions.php (use the after_setup_theme hook so the constant exists by the time the plugin reads it): add_action( 'after_setup_theme', static function () { if ( ! defined( 'TSCSSCOMPILER_PAIRS' ) ) { define( 'TSCSSCOMPILER_PAIRS', [ [ 'scss_path' => 'assets/scss/style.scss', 'css_path' => 'assets/css/style.css', 'version' => '1.0.0', 'context' => 'frontend' ], ] ); } } ); 3. .env + wp-config.php (Bedrock-style): .env TSCSSCOMPILER_AUTO_ENQUEUE=true TSCSSCOMPILER_OUTPUT_STYLE=compressed wp-config.php (or config/application.php in Bedrock) if ( getenv( 'TSCSSCOMPILER_AUTO_ENQUEUE' ) !== false ) { define( 'TSCSSCOMPILER_AUTO_ENQUEUE', filter_var( getenv( 'TSCSSCOMPILER_AUTO_ENQUEUE' ), FILTER_VALIDATE_BOOLEAN ) ); } if ( $style = getenv( 'TSCSSCOMPILER_OUTPUT_STYLE' ) ) { define( 'TSCSSCOMPILER_OUTPUT_STYLE', $style ); } Pairs as a deep array don't fit naturally in .env — define them in wp-config.php (or config/application.php in Bedrock) instead.

That means TSCSSCOMPILER_PAIRS is defined somewhere (wp-config, theme, .env bridge). The form is intentionally read-only in that state — to make changes, edit the source where the constant is defined. Boolean toggles like …_AUTO_COMPILE defined via constants are also reflected as locked switches.