Title: Reloadify Frontend Sync
Author: Shaoun Chandra Shill
Published: ሓምለ 21, 2026
Last modified: ሓምለ 29, 2026
---
Search plugins
# Reloadify Frontend Sync
By [Shaoun Chandra Shill](https://profiles.wordpress.org/shaounchandrashill/)
[Download](https://downloads.wordpress.org/plugin/reloadify-frontend-sync.1.1.1.zip)
* [Details](https://tir.wordpress.org/plugins/reloadify-frontend-sync/#description)
* [Reviews](https://tir.wordpress.org/plugins/reloadify-frontend-sync/#reviews)
* [Installation](https://tir.wordpress.org/plugins/reloadify-frontend-sync/#installation)
* [Development](https://tir.wordpress.org/plugins/reloadify-frontend-sync/#developers)
[Support](https://wordpress.org/support/plugin/reloadify-frontend-sync/)
## Description
**Reloadify Frontend Sync** is a developer and QA tool designed to streamline the
workflow when building sites with page builders like **Elementor** and **Divi**.
Instead of manually refreshing your frontend every time you save a change, **Reloadify
Frontend Sync** automatically reloads every connected browser or window, keeping
all your frontend previews synchronized without interrupting your workflow.
#### Why Use Reloadify?
Manually refreshing the frontend after every save interrupts your workflow and wastes
time, especially when testing across multiple browsers.
Reloadify Frontend Sync keeps every open browser automatically synchronized, allowing
you to focus on building instead of constantly refreshing.
#### Key Features
* Works with **Elementor**, **Divi**, **Bricks**, **Oxygen**, **Beaver Builder**,**
WPBakery Page Builder**, and the classic WordPress editor.
* Cross-browser, cross-window reload — enabled out of the box for Chrome, Brave,
Edge, Firefox, Safari, Opera, and UC Browser, normal and incognito/private alike.
* Reloads any frontend page (home, archives, search results — not just the exact
post you’re editing).
* Choice of soft reload or cache-busting hard reload.
* A **Last change detected** readout with a one-click **Check now** button, so
you can confirm the plugin picked up a save without waiting for a frontend tab
to reload.
* A modern settings dashboard with per-browser cards and live status.
* **Speed Boost** — on by default: strips the emoji script, trims unused `` tags, throttles the Heartbeat API, caps stored post revisions, disables self-
pingbacks, and eases wp-admin memory/time limits for heavy builders — all reversible
with one toggle.
* **Media Optimization** — on by default: new image uploads get WebP/AVIF versions
automatically (Automatic picks the best your server supports, or pin WebP/AVIF
yourself), video is compressed in the background when ffmpeg is available, offscreen
images and embedded video are lazy-loaded, and a new **Optimization** column
in the Media Library shows the real, measured size saved on every file.
* **Extensions tab** — optional SVG upload support (off by default; scanned for
scripts/embedded HTML before accepting) and an optional Scroll To Top floating
button (off by default; configurable position and color).
* An honest Server Performance panel: applies memory_limit / max_execution_time
automatically, and generates ready-to-paste php.ini / .htaccess snippets for
the settings a plugin genuinely cannot change at runtime (opcache, upload/post
size limits, realpath cache).
* Intelligent exclusion: never triggers a reload loop inside the builder canvas
itself.
#### Works With
Reloadify Frontend Sync has been tested with:
* WordPress Block Editor (Gutenberg)
* Classic Editor
* Elementor
* Divi
* Bricks Builder
* Oxygen Builder
* Beaver Builder
* WPBakery Page Builder
* Most WordPress themes
#### Video
#### How It Works (for end users)
1. Install and activate the plugin — no configuration needed to start; everything
works out of the box.
2. Open your page in the builder (Elementor, Divi, etc.) in one browser tab.
3. Open the same page’s live frontend view in another tab, another window, or even
another browser entirely.
4. Make a change and save it in the builder as normal.
5. The frontend tab reloads on its own within a couple of seconds — no manual refresh
needed.
6. If you ever need to fine-tune behavior (turn off a specific browser, switch to
hard reload, check server settings), go to **Auto Reloader** in your wp-admin sidebar.
### Feedback
If Reloadify Frontend Sync improves your workflow, please consider leaving a review
on WordPress.org.
Your feedback helps improve the plugin and supports future updates.
## Screenshots
[⌊Cross-Browser Reload tab — Developer Mode toggle, live browser/reload-mode status,
soft vs hard reload choice, and per-browser normal/incognito controls for Chrome,
Brave, Edge, Firefox, Safari, Opera, and UC Browser.⌉⌊Cross-Browser Reload tab —
Developer Mode toggle, live browser/reload-mode status, soft vs hard reload choice,
and per-browser normal/incognito controls for Chrome, Brave, Edge, Firefox, Safari,
Opera, and UC Browser.⌉[
Cross-Browser Reload tab — Developer Mode toggle, live browser/reload-mode status,
soft vs hard reload choice, and per-browser normal/incognito controls for Chrome,
Brave, Edge, Firefox, Safari, Opera, and UC Browser.
[⌊Server Performance tab — live PHP/OPcache values the plugin applies at runtime,
plus the settings that require host-level changes, each clearly marked LIVE and
AUTO-ATTEMPT.⌉⌊Server Performance tab — live PHP/OPcache values the plugin applies
at runtime, plus the settings that require host-level changes, each clearly marked
LIVE and AUTO-ATTEMPT.⌉[
Server Performance tab — live PHP/OPcache values the plugin applies at runtime,
plus the settings that require host-level changes, each clearly marked LIVE and
AUTO-ATTEMPT.
[⌊Extensions tab — optional SVG upload support (off by default) and the Scroll To
Top floating button controls (position, color, and scroll-distance threshold).⌉⌊
Extensions tab — optional SVG upload support (off by default) and the Scroll To
Top floating button controls (position, color, and scroll-distance threshold).⌉[
Extensions tab — optional SVG upload support (off by default) and the Scroll To
Top floating button controls (position, color, and scroll-distance threshold).
## Installation
1. Upload the plugin files to `/wp-content/plugins/reloadify-frontend-sync`, or install
through the WordPress plugins screen.
2. Activate the plugin.
3. Open a page in your builder in one tab/browser, and the frontend view in another(
any browser, any window).
4. Save in the builder — the frontend reloads on its own.
5. Visit **Auto Reloader** in the wp-admin sidebar to fine-tune Developer Mode, reload
behavior, per-browser settings, and server performance.
## FAQ
### Why doesn’t it reload in a particular browser?
Check Auto Reloader Cross-Browser Reload: confirm Developer Mode is on and that
browser/mode is toggled on. Everything is on by default, but if you turned things
off before, check there first.
### Is incognito/private mode detection 100% reliable?
No — it’s a best-effort heuristic. Several browsers deliberately make private mode
indistinguishable from normal mode. When it can’t tell, the plugin defaults to running
the reloader anyway rather than staying silent.
### Does the Server Performance panel really change opcache/upload limits?
memory_limit, max_execution_time, and three of the six opcache.* directives (enable,
validate_timestamps, revalidate_freq) genuinely can be applied live by any WordPress
plugin — that’s just how PHP classifies them. The other three opcache directives(
memory_consumption, interned_strings_buffer, max_accelerated_files) size shared
memory once at PHP startup and truly can’t be touched without editing php.ini and
restarting PHP — same for post_max_size, upload_max_filesize, and realpath cache.
For those, the panel writes a best-effort .user.ini/.htaccess (works on many hosts)
or generates a copy-paste snippet, instead of pretending to apply them for you.
### Should I leave Developer Mode on in production?
No — turn it on only while you’re actively testing, then switch it back off yourself.
It’s off by default for exactly this reason: while it’s on, every visitor’s browser
polls the server, which is fine for staging but adds real load with real traffic.
Unlike earlier versions, Developer Mode no longer disables itself automatically —
it stays exactly as you set it until you change it, so remembering to switch it
off is now on you.
### Will this slow my site down?
The frontend check is a small static file the webserver answers directly — no PHP
or WordPress involved — so it’s cheap per check. The main thing that adds load is
leaving Developer Mode on for a long time on a busy live site, since every visitor’s
browser then polls continuously; keep it switched on only while you’re actually
testing.
### Does Media Optimization touch my original uploaded files?
No. For images, the original file you uploaded is never modified — only the generated
thumbnail/medium/large sizes get WebP or AVIF versions alongside them, and only
if your server’s image library actually supports that format (checked with WordPress’s
own detection, never assumed). Video compression only runs if the server has ffmpeg
available; if it doesn’t, video is left completely untouched rather than pretending
to optimize it. The whole feature is one toggle — turn it off any time to leave
media exactly as WordPress would handle it by default.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Reloadify Frontend Sync” is open source software. The following people have contributed
to this plugin.
Contributors
* [ Shaoun Chandra Shill ](https://profiles.wordpress.org/shaounchandrashill/)
[Translate “Reloadify Frontend Sync” into your language.](https://translate.wordpress.org/projects/wp-plugins/reloadify-frontend-sync)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/reloadify-frontend-sync/),
check out the [SVN repository](https://plugins.svn.wordpress.org/reloadify-frontend-sync/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/reloadify-frontend-sync/)
by [RSS](https://plugins.trac.wordpress.org/log/reloadify-frontend-sync/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.1.1
* Fixed a video compression bug on Windows servers: the background ffmpeg command
included `nice`, a Unix-only process-priority tool with no Windows equivalent,
so the entire command failed to run there and video was silently never compressed(
the original file was never at risk — this plugin only ever swaps a video if
compression reports success — but Windows/local-dev users got zero benefit from
the feature). Also hardened the success check so an implausibly small/truncated
encode is rejected instead of accepted.
* New: Media Optimization image format is now a real choice — **Automatic** (default;
picks the best your server supports), **WebP only**, or **AVIF only** — instead
of always being decided for you. Choosing AVIF on a server that can’t produce
it falls back to WebP automatically rather than silently converting nothing.
* Fixed: the help (i) icons were using the browser’s native tooltip (the plain `
title` attribute), which can’t be styled or positioned and could render overlapping
adjacent labels depending on cursor position. Replaced with a proper tooltip
component — dark, rounded, positioned consistently below its icon, and it no
longer clips or overlaps surrounding text.
* Renamed the **Extra Features** tab to **Extensions**.
* Fixed: **SVG Upload Support** defaulted to on, which didn’t match this plugin’s
own documented intent (loosening a WordPress security default should be an explicit
opt-in, never automatic) or the Scroll To Top button’s existing off-by-default
behavior. Both now default to off; nothing changes for anyone who already explicitly
turned either one on.
* Updated the Bengali (bn_BD) translation to cover the new format-choice control
and the Extensions tab name.
#### 1.1.0
* New **Extra Features** tab: optional SVG upload support (on by default — every
upload is scanned for `