Production website optimization

Website ZIP Optimizer

Upload a static website ZIP, check eligibility for free, then optimize supported HTML, CSS, and JavaScript files for a one-time USD $5.00 payment.

  • Up to 75 processable code files
  • Paths and safe static assets preserved
  • Private, expiring result download
One website ZIP $5.00 USD · one-time payment

The eligibility scan is free. You pay only after the ZIP passes the current limits.

Free step 1 of 2

Check your website ZIP

No payment during this scan
No file selected. .zip only · maximum 25 MB

We inspect archive structure and counts only. Optimization begins only after verified payment.

Clear, two-step workflow

Scan first. Pay only when eligible.

01

Upload and validate

We check ZIP safety, supported code-file counts, archive size, and current service limits.

02

Review before payment

See the exact HTML, CSS, JavaScript, preserved asset, and excluded-file counts.

03

Pay and optimize

Stripe confirms the one-time payment before background processing can start.

04

Test the result

Download the protected output, review the report, and test the website before deployment.

Current service limits

What the $5.00 job includes

The processable-file limit counts only non-minified .html, .htm, .css, and .js files selected for optimization. Safe assets and already-minified files do not use that allowance.

Processable code files
Up to 75
Upload size
Up to 25 MB
Result retention
24 hours
Price
USD $5.00
Predictable output

Files we process, preserve, and exclude

Optimized

.css, .htm, .html, .js

Preserved unchanged

Safe images, fonts, documents, data, and map files including .avif, .eot, .gif, .ico, .jpeg, .jpg, .json, .map, .otf, .pdf, .png, .svg, .ttf, .txt.

Excluded

Executable, server-side, archive, secret, and unsupported files. Examples: .bash, .bat, .cmd, .config, .db, .dll, .env, .exe, .ini, .jar, .key, .pem.

Minification is conservative, but production websites vary. Always test the optimized ZIP before replacing a live deployment.

Service questions

Website ZIP Optimizer FAQ

How much does Website ZIP Optimizer cost?

One eligible website ZIP costs USD $5 as a one-time payment. The eligibility scan is free and payment is requested only after the archive passes the current limits.

What counts toward the 75-file limit?

Only non-minified .html, .htm, .css, and .js files selected for optimization count. Safe static assets and files named like app.min.js or style.min.css do not use the allowance.

Does the free scan change or optimize my files?

No. The free scan validates ZIP structure, safety limits, supported file types, and counts. Code optimization begins only after Stripe confirms payment.

Will the optimized ZIP keep the same folder structure?

Yes. Supported code and approved static assets keep their safe relative paths and file names in the output archive.

Which files are minified?

The service minifies supported UTF-8 HTML, HTM, CSS, and JavaScript files. It does not obfuscate JavaScript or process server-side code.

What happens to images, fonts, JSON, XML, PDFs, and source maps?

Approved static asset types are copied byte-for-byte without being minified. Blocked and unsupported files are excluded and listed in the scan summary.

Do I need a ScriptZip account?

No. Guest checkout is supported. The private job link is available in the browser session used for the upload, so keep that session open until the result is downloaded.

How long are uploaded and optimized ZIP files kept?

Source and result ZIP files are temporary and scheduled for deletion after the configured retention window, currently 24 hours. Download the result before it expires.

Can I upload WordPress, PHP, or other server applications?

The service is intended for static website archives. PHP, Python, executables, secrets, nested archives, and other blocked or unsupported files are not processed and may be excluded.

What should I do if a paid job fails?

Use the private job reference to contact support. We review the payment and processing record and determine whether a retry or refund is appropriate. Always test successful output before deployment.

Prefer a single-file workflow?