Is JSM Force HTTP to HTTPS / SSL safe to install?
Good choice: actively maintained
- Pass: Actively maintained Last updated 3 weeks ago (version 3.5.0).
- Pass: Compatible with current WordPress Tested up to WordPress 7.1; the current release is 7.1. Needs PHP 7.4.33+.
- Pass: Well rated Rated 5.0/5 by 13 users on WordPress.org.
- Pass: Widely used Active on 6,000+ sites.
Check every plugin on your site with the free WordPress plugin checker →
Based on WordPress.org data, checked Nov 19, 2026. Always keep plugins updated and test changes on a staging site.
Overview
JSM Force HTTP to HTTPS / SSL describes itself as: “No setup required - simply activate to force HTTP URLs to HTTPS using native WordPress filters and permanent redirects for best SEO.”
It is active on 6,000+ WordPress sites and rated 5.0 out of 5 by 13 users on WordPress.org.
Downloads & growth
How often JSM Force HTTP to HTTPS / SSL is downloaded from WordPress.org each day, over the last 90 days.
Source: WordPress.org download statistics. Downloads include updates on existing sites, so tall spikes usually mark a new release. See what's trending →
How to install JSM Force HTTP to HTTPS / SSL
- Open the plugin installer. In your WordPress dashboard go to Plugins → Add New Plugin.
- Search for it. Type “JSM Force HTTP to HTTPS / SSL” and pick the one by JS Morisset.
- Install and activate. Click Install Now, then Activate.
Install with a zip file or WP-CLI
Download the zip from the WordPress.org plugin page, then go to Plugins → Add New Plugin → Upload Plugin, choose the file and click Install Now. Or from the command line:
wp plugin install jsm-force-ssl --activateRequirements: WordPress 6.0+ · PHP 7.4.33+ · tested up to WordPress 7.1.5
Hooks & customisation
The hooks reference for this plugin is being generated and will appear here shortly.
JSM Force HTTP to HTTPS / SSL: frequently asked questions
Is JSM Force HTTP to HTTPS / SSL free?
Yes. JSM Force HTTP to HTTPS / SSL is free to download from the official WordPress.org plugin directory and is licensed under the GPL, so you can use it on as many sites as you like. Some developers sell a separate Pro version or paid add-ons; check the developer's website for details.
Is JSM Force HTTP to HTTPS / SSL safe to use?
JSM Force HTTP to HTTPS / SSL is actively maintained: the latest version was released 3 weeks ago. Users rate it 5.0 out of 5 from 13 reviews on WordPress.org. As with any plugin, keep it updated and only install it from WordPress.org or the developer.
Does JSM Force HTTP to HTTPS / SSL work with WordPress 7.1?
Yes. JSM Force HTTP to HTTPS / SSL is tested up to WordPress 7.1, the current release. It requires WordPress 6.0 or later and PHP 7.4.33 or later.
How many websites use JSM Force HTTP to HTTPS / SSL?
JSM Force HTTP to HTTPS / SSL is active on 6,000+ WordPress sites, according to WordPress.org. It is currently at version 3.5.0, last updated on October 29, 2026.
What are the best alternatives to JSM Force HTTP to HTTPS / SSL?
Plugins that do a similar job and are actively maintained include WP Force SSL & HTTPS SSL Redirect (80,000+ installs), SSL Insecure Content Fixer (100,000+ installs), SSL Zen (9,000+ installs).
Can I customise JSM Force HTTP to HTTPS / SSL without editing its code?
JSM Force HTTP to HTTPS / SSL doesn't expose its own hooks, so changing its behaviour usually means a small companion plugin. Tell us what you need and we'll suggest the safest way.
Done for you
Need JSM Force HTTP to HTTPS / SSL to do more?
Clear starting prices, an exact quote before any work, and changes built so plugin updates never wipe them.
Plugin customisation
from $149
New features or changed behaviour, without editing the plugin’s files.
- Built as a companion plugin, so updates never wipe it
- Exact quote before we start
- Tested on staging, then deployed
Typical turnaround: 3–7 business days
Choose thisCustom hook snippet
from $49
A small, update-safe change built on the plugin’s own hooks.
- Code written against the plugin’s actions and filters
- Tested on a staging copy of your site
- Install instructions included
Typical turnaround: 2–3 business days
Choose thisBug or conflict fix
from $79
Errors, broken layouts or two plugins that don’t get along.
- Find the cause on a staging copy
- Fix without breaking updates
- Explain what was wrong
Typical turnaround: 1–3 business days
Choose thisNot sure which fits? Describe what you need and we’ll suggest the simplest option.
Need JSM Force HTTP to HTTPS / SSL customised?
Tell us what you want changed, added or fixed and we'll reply with an estimate.
WP EXPERTS is independent and not affiliated with JS Morisset. Plugin names and logos belong to their owners. Version, rating and install figures from WordPress.org, checked Nov 19, 2026.