Static Porter
Convert WordPress to blazing-fast static HTML. Deploy to Cloudflare, AWS S3 + CloudFront, or download as ZIP. Safe for shared hosting.
Solide Wahl
Static Porter is a solid plugin choice in 2026, with a few things worth checking first. It runs on 100+ sites, is rated 5/5 and was last updated 1 month ago, and scores 79/100 on our health check.
- Actively developed — last update 1 month ago
- Getestet mit dem neuesten WordPress (7.1)
- Kleine Benutzerbasis (100+ aktive Installationen)
- Bisher sehr wenige Bewertungen
Wie stapelt es sich?
Side-by-side bei Installationen, Updates, Bewertungen und SupportTägliche Downloads
Download-Spitzen folgen normalerweise einer neuen Version - jede Website, die automatisch aktualisiert wird, gilt als Download.
Ranglisten
Where Static Porter stands todayWordPress.org Ranglisten suchen
Live-Position in der Plugin-Suche, Top 100| Stichwort | Position |
|---|---|
| amazon s3 | #36 |
| cdn | >100 |
| cloudflare | >100 |
| Performance | >100 |
| static site generator | #5 |
Versionsübernahme
Anteil aktiver Sites pro Release.
Bewertungsaufschlüsselung
★★★★★★★★★★ 5 from 1 reviews
About Static Porter
From the official readme · v4.3.0Beschreibung
Static Porter turns your WordPress site into pre-built HTML files, so visitors get instant page loads without your server ever touching PHP or a database.
Most caching plugins just speed up WordPress. Static Porter goes further: it generates a real, physical copy of your site that can be served on its own — from your own server via Apache, from Cloudflare’s global edge network, from an AWS S3 bucket behind CloudFront, or as a downloadable ZIP you can host anywhere. Your live WordPress site stays completely private and secure behind the scenes; only the static HTML is ever exposed to visitors.
Built with shared and budget hosting in mind: a live “Peak Memory” monitor, a one-click “Stop Crawl” safety switch, and sensible defaults mean you’re never one crawl away from taking your server down.
Automated Maintenance (Smart Refresh)
Never worry about stale content. When you publish or update a post, Static Porter quietly regenerates that post, your homepage, and its category and tag archives in the background, without slowing down the editor. Unpublish, trash, or rename a post and its old static file is removed automatically, so visitors never get served a page that no longer exists.
Why choose Static Porter?
- Deploy anywhere: Not locked into one platform. Serve statically from your own Apache server, push to Cloudflare Workers, upload to AWS S3 with automatic CloudFront cache invalidation, or export a portable ZIP — pick whichever fits your infrastructure.
- Built for real-world WordPress: Works with page builders, shortcodes, and JavaScript-driven widgets. A built-in Documentation tab explains exactly what works out of the box and what needs a small adjustment first (forms, WooCommerce checkout, etc.).
- Tells you what won’t work before you crawl: A built-in Compatibility check tests your real site for blocked crawling, plain permalinks, form and shop plugins, and pages that contain forms or checkout content, and can add the right exclusions for you.
- Safe by default: Every feature that could meaningfully change your site’s output — Cloudflare deployment, S3 deployment, asset mirroring — is hidden until you explicitly turn it on. Nothing surprises you.
Hauptmerkmale
Static generation & speed
* One-Click Full Crawl: Generate a static version of your entire site in one click.
* Server-Safe Crawling: A real-time “Peak Memory” monitor and an emergency “Stop Crawl” button, designed for budget shared hosting where resources are limited.
* Smart Refresh: Publishing or updating a post regenerates that page, your homepage, and its archives in the background. Unpublished, trashed, and renamed posts have their old files removed.
* Crawl Health Report: After every crawl, see exactly how many pages were cached and which failed, with the reason for each (timeout, HTTP 500, HTTP 403) and one-click Retry. Error pages are never saved as static files.
* Orphan File Cleanup: Finds static files whose source page was deleted, unpublished, renamed, or excluded, explains why, and removes them manually or automatically after each crawl.
* Advanced Optimization: Built-in HTML minification and Gzip compression.
* Security & Caching: Automatically configures .htaccess with security headers and browser caching rules.
* NGINX Support: Detects NGINX and generates the exact server rule your site needs, with a copy button. The Dashboard status is honest about whether pages are actually being served.
Deploy anywhere
* Cloudflare Deployment: Push your static files straight to a Cloudflare Worker, serving your site from Cloudflare’s global edge network. Hidden until you enable it.
* AWS S3 + CloudFront Deployment: Upload directly to an S3 bucket, with automatic CloudFront cache invalidation on every deploy. Hidden until you enable it.
* Asset Mirroring: Optionally copy your CSS, JavaScript, images, and fonts locally too, so a deployed or exported site works completely standalone — no dependency on your WordPress server staying online.
* Download as ZIP: Export your entire static site as a single ZIP file — perfect for local browsing, migrating hosts, or keeping an offline snapshot.
Visibility & control
* Persistent Cache Table: See every cached page with five independent actions per row: View, Recrawl, Copy URL, Exclude, and Delete — each with clear confirmation and feedback.
* File Storage Location: See exactly where your static HTML files live on disk, with a one-click “Copy path” button and a writable/not-writable status check.
* Compatibility Check: A dedicated tab that scans your site before the first crawl and flags anything that behaves differently as static pages, with a one-click button to add suggested exclusions.
* Built-in Documentation: A dedicated Documentation tab covers every feature — how it works, file locations, compatibility, deployment options, and FAQs — without ever leaving wp-admin.
Installation
- Laden Sie den Ordner
static-porterin das/wp-content/plugins/-Verzeichnis hoch. - Aktivieren Sie das Plugin über das „Plugins“-Menü in WordPress.
- Go to the ‘Static Porter’ menu in your sidebar.
- Open the ‘Compatibility check’ tab to see whether anything on your site needs attention.
- Configure your excluded paths and click ‘Start full crawl’.
- On NGINX, add the server rule shown on the Dashboard (Apache and LiteSpeed work automatically).
Änderungsprotokoll
Adds an optional setting that makes lightbox and gallery image links (Divi lightboxes, for example) work in exports and deployments. Includes the 4.2.2 security fixes.
4.3.0
- New: “Also mirror links to images” option under Asset Mirroring. Page builders such as Divi wrap thumbnails in a link to the full-size photo (for example the Divi lightbox). With this option on, those links are rewritten to local paths and the full-size images are saved, so lightboxes work in ZIP exports and in Cloudflare and S3 deployments. Only links that go straight to an image on your own site are changed. Page links, documents, other sites’ images, canonical URLs, og:image tags, and structured data keep their absolute addresses. It is off by default because it downloads full-size images. Thanks to the user who suggested it.
4.2.2
- Security: Asset Mirroring now saves only known static file types (images, fonts, stylesheets, JavaScript and SVG). Each download must match its file type, contain no server-side code, and stay within a size limit. Executable and configuration file types, hidden files, and unsafe or traversal-style paths are refused.
- Security: External asset mirroring now contacts only public internet addresses, with HTTPS certificates verified. Internal network addresses and this server’s own other ports are never requested, and the number of downloads per request is capped.
- Security: Crawl, retry, and exclude actions now accept only URLs that belong to this site. A redirect is followed only while it stays on this site, and every destination path is checked to stay inside the cache folder.
- Security: AWS S3, CloudFront, and Cloudflare settings are validated before they are used to build requests, and request data handling in the settings screen was tightened.
- Fix: Asset Mirroring no longer rewrites link tags such as canonical and alternate URLs, and relative URLs inside a mirrored external stylesheet now resolve against that stylesheet’s own address.
- Changed: Files whose names contain spaces or encoded characters are no longer mirrored; they keep pointing at their original address. Loopback requests to your own site still accept self-signed certificates, as WordPress does by default (adjustable with the https_local_ssl_verify filter).
4.2.1
- Fix: AWS S3 uploads and CloudFront cache invalidation could fail with a signature error. A second copy of the Content-Type header, differing only in letter case, was being sent alongside the signed one, which invalidates the request signature. Thanks to the user who reported it.
- Fix: S3 object keys are now encoded the way AWS requires when signing a request. Files with characters such as @, spaces, parentheses, + or non-English letters in their names (for example logo@2x.png) now upload correctly instead of failing with SignatureDoesNotMatch.
4.2.0
- New: Crawl health report. When a crawl finishes you see pages cached, pages failed, and duration, with every failure listed alongside its reason (timeout, HTTP 500, HTTP 403) and a Retry button, plus Retry all failed. The report is saved, so it is still there after a reload.
- New: Orphan file cleanup. Detects static files whose source was deleted, trashed, unpublished, scheduled, made private, renamed (shown with the new URL), excluded, or switched off under Content to crawl. Delete or Ignore each one, Delete all, or tick “Auto-delete orphans after each crawl”. Deletion is re-verified on the server and empty folders are removed.
- New: NGINX support. NGINX is detected, and a ready-to-copy server rule equivalent to the .htaccess rule is generated for your site’s real paths, including subdirectory installs. The status badge now reads “Generated” instead of “Active” on NGINX, because nothing is served statically until the rule is added.
- New: Compatibility check tab. Tests that crawling works (and explains HTTP 401 and 403 blocks), flags plain permalinks, checks the server type, cache folder, and .htaccess rules, detects form, shop, membership, and competing page-cache plugins, and scans your pages for forms, cart, checkout, and login content, including Divi and Elementor forms. One click adds the suggested exclusions. The homepage is never suggested for exclusion.
- Improved: Smart Refresh now also regenerates the posts page and the post’s category and tag archives, removes the old file when a post is unpublished, trashed, deleted, or its URL changes, refreshes a post when a comment is approved, handles scheduled posts going live, and runs after the editor has saved so you never wait on it. It respects Content to crawl and Excluded paths. A “full crawl recommended” banner appears when menus, widgets, the theme, permalinks, or active plugins change, since Smart Refresh can’t see those.
- Fix: Pages that return an HTTP error (404, 500, and so on) are no longer saved as static files. Previously an error page could be cached and served to visitors. If a refresh fails, the existing good copy is now kept.
- Fix: Deploying to Cloudflare or S3 with Asset Mirroring on now actually uploads the mirrored CSS, JavaScript, images, and fonts, not just the HTML, and sends each file with the correct content type instead of labeling everything as HTML.
- Fix: Asset Mirroring now also covers responsive images (srcset), no longer skips re-downloading assets after the cache is purged, and no longer logs a PHP warning on every asset.
- Security: Every crawl, delete, and stats request now checks administrator capability as well as the nonce, and file paths from the browser are validated to stay inside the cache folder.
- Requirement: Smart Refresh relies on a hook introduced in WordPress 5.6, so the minimum WordPress version is now 5.6.
4.1.0
- Redesign: Cloudflare deployment is no longer shown as an always-visible settings card. It now appears as a compact “Enable” card by default, and only expands into the full account ID / API token / worker name settings — and only shows the “Deploy to Cloudflare” button in the actions row — once you explicitly enable it. Existing Cloudflare credentials are preserved if you disable and later re-enable it.
- New: Added a Cloudflare-branded icon to the deployment card in place of the generic cloud icon.
- New: Added a “Documentation” tab directly on the plugin’s own dashboard page (next to “Dashboard”), covering how the plugin works step by step, exact file storage locations, a compatibility guide (shortcodes, forms, sliders, WooCommerce, NGINX), and frequently asked questions — no need to leave wp-admin to understand what the plugin does.
- Redesign: The Cached pages table’s single Delete/Recrawl toggle button has been replaced with five independent row actions: View (opens the generated static file directly), Recrawl (regenerates that page without deleting it first), Copy URL, Exclude (adds the page’s path to Excluded Paths and removes its static file in one step), and Delete. Delete now shows an inline “Delete this static file?” confirmation in place of the row instead of deleting immediately, Recrawl shows a spinning icon and briefly disables the row while it runs, and Copy/Exclude flash a green checkmark to confirm the action completed.
- Expanded: The Documentation tab now covers every feature in the plugin across nine sections — How it works, Crawling and content, Performance and output, File locations, Cached pages actions, Cloudflare deployment, Download ZIP, Compatibility, and FAQ — instead of the original four thin sections.
- New: Added a red “New” badge on the Documentation tab, and a dismissible callout banner on the Dashboard pointing new users to it. Both automatically stop showing once you’ve visited the Documentation tab at least once, or if you dismiss the banner directly.
- New: Added optional AWS S3 + CloudFront deployment. Enable it from a collapsed settings card (matching the Cloudflare card’s pattern, but visually distinct with an AWS-branded bucket icon and navy color treatment) to reveal fields for your AWS Access Key ID, Secret Access Key, S3 bucket name, region, and an optional CloudFront distribution ID. Deploying uploads your static files to S3 using hand-implemented AWS Signature Version 4 request signing (no AWS SDK dependency), and automatically invalidates your CloudFront cache afterward if a distribution ID is set.
- New: Added optional Asset Mirroring. When enabled, Static Porter downloads a local copy of every CSS, JavaScript, image, and font file a page references — including assets referenced inside CSS via url() and @import — and rewrites the page to point at those local copies. This makes ZIP exports and Cloudflare/S3 deployments fully standalone, no longer dependent on your WordPress site staying online to serve styling and images. A separate sub-option extends mirroring to external, third-party assets like Google Fonts. A warning banner appears near the deploy and download buttons whenever this is off and a deployment feature is active, so you know before you deploy rather than after.
- Fix: The “Download ZIP” button is now disabled and labeled “Crawl first to download as ZIP” until at least one page has been crawled, instead of being clickable and failing with an error afterward.
- Docs: Expanded the Documentation tab with two new sections, Asset Mirroring and S3 + CloudFront, and corrected the Cloudflare and Download ZIP sections to reflect that assets can now be included when Asset Mirroring is turned on.
- Docs: Added a new SEO section to the FAQ answering whether a new sitemap.xml is needed (no — Static Porter never touches it), whether Asset Mirroring affects sitemap image links (no), and what to check for SEO after using the plugin.
4.0.0
- New: Added a “File storage location” settings card showing the full server path and browser-accessible URL of the static file cache, a writable/not-writable status indicator, a one-click “Copy path” button, and a direct “Open in browser” link.
- New: Added a “Download ZIP” button that packages your entire static HTML output into a single ZIP file and triggers an automatic browser download. Useful for local site browsing, migrating to a different host, or sharing a snapshot of the static output. Requires PHP’s ZipArchive extension (available on all major hosts).
Für Entwickler
Ist das dein Plugin? Zeigen Sie die Zahlen.
Fügen Sie Ihrer Website, Docs oder GitHub Readme ein Live-Badge hinzu. Es wird von selbst aktualisiert - kein Konto erforderlich.
Best Static Porter alternatives
All amazon s3 plugins →Fragen und Antworten
Static Porter: quick answers
Gerade Antworten, gezogen von Live WordPress.org Daten.
Quelle: WordPress.org
Is Static Porter free?
Yes. Static Porter is free to download and use from the official WordPress.org plugin directory.
Is Static Porter safe to use in 2026?
Static Porter is a solid plugin choice in 2026, with a few things worth checking first. It runs on 100+ sites, is rated 5/5 and was last updated 1 month ago, and scores 79/100 on our health check.
How many websites use Static Porter?
Static Porter is active on 100+ WordPress websites and has been downloaded 2,760 times since it launched in January 2026. It was downloaded 633 times in the last 30 days.
Does Static Porter work with WordPress 7.1?
Yes. The developer has tested Static Porter up to WordPress 7.1.5, the latest release. It requires WordPress 5.6 or newer.
What PHP version does Static Porter need?
Static Porter requires PHP 7.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Static Porter last updated?
The latest version, 4.3.0, was released on October 21, 2026 (1 month ago).
Who makes Static Porter?
Static Porter is developed and maintained by Kayıhan Turgutoğlu.
What are the best alternatives to Static Porter?
The most popular alternatives to Static Porter are WP Offload Media Lite for A… (30K+ installs), Advanced Media Offloader (8K+ installs) and Offload Media (1K+ installs).
Angetrieben von PageForge
Eine Vorlage und eine Tabelle. Eine echte Seite für jede Suche.
PageForge Verwandelt jede Zeile eines CSV in eine WordPress-Seite mit eigenem Titel, URL, SEO Felder und Schema entworfen. Kostenlos auf WordPress.org.
- CSV und XLSX, plus Google Sheets auf Beruf und Unternehmen
- seinen eigenen Titel, URL, SEO Felder und Schema für jede Seite
- Arbeitet mit dem Blockeditor, Elementor, Divi und Avada
- Kostenlos auf WordPress.org, keine Kreditkarte





