Commissioned Research
Top 10 Best Lossless Compression Software of 2026

GITNUXSOFTWARE REVIEW

Technology & Digital Media

Top 10 Best Lossless Compression Software of 2026

Compare lossless compression software tools and use-case fit, with tradeoffs for file sizes and quality, plus ImageOptim, Squoosh, and alternatives.

19 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Lossless compression tools reduce storage and transfer size without changing content, which matters for archives, backups, and compliance-friendly workflows. This roundup helps scanners compare format handling, metadata behavior, and automation paths across Windows and macOS, using concrete tradeoffs like toolchain compatibility and archive integrity.

ImageOptim is the best pick for macOS users running repeatable batch jobs on lossless PNGs and similar images because it auto-picks per-format lossless optimizers inside one queue, whereas NX Power Lite Desktop fits teams with mixed Office and PDF folders since it preprocesses losslessly with integrity verification per run.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

ImageOptim

Automatic selection of per-format lossless optimizers inside a single queue workflow, reducing manual encoder switching.

Best for: Fits when a macOS workflow needs lossless PNG and related re-encodes in repeatable batch jobs.

2

NX Power Lite Desktop

Editor pick

Content-aware lossless preprocessing that selects per-format packing behavior and verifies integrity per run.

Best for: Fits when teams need repeatable lossless compression for mixed file folders.

3

Squoosh

Editor pick

Side-by-side encode and size comparison built for interactive, per-asset testing in the browser.

Best for: Fits when image files need quick lossless size comparisons without installing compression software.

Comparison Table

1
ImageOptimBest overall
vertical specialist
9.1/10
Overall
2
8.8/10
Overall
3
vertical specialist
8.6/10
Overall
4
SMB
8.4/10
Overall
5
API-first
8.2/10
Overall
6
7.9/10
Overall
7
7.6/10
Overall
8
developer
7.1/10
Overall
9
6.9/10
Overall
10
developer
6.6/10
Overall
#1

ImageOptim

vertical specialist

ImageOptim reduces image file sizes through lossless optimization and metadata removal on macOS.

9.1/10
Overall
Features9.1/10
Ease of Use9.0/10
Value9.2/10
Standout feature

Automatic selection of per-format lossless optimizers inside a single queue workflow, reducing manual encoder switching.

ImageOptim provides lossless image size reduction by re-encoding supported raster formats without changing visible pixels. The workflow is macOS-first and centers on queue-based processing so batches of files can run consistently rather than one-off manual edits. It also includes a command-line interface so optimized outputs can be generated as part of build or release steps.

A practical tradeoff is that it is designed around common raster formats and a macOS-oriented workflow rather than a cross-platform, server-first image service. It is a good fit when image files must be transformed before upload or publishing, and when the goal is smaller file sizes without altering what the viewer sees.

The typical usage pattern is to point ImageOptim at a folder of images, apply deterministic optimization rules, and then review the resulting files for consistent delivery behavior. Teams often pair the CLI option with scripts to preprocess images before they land in a CMS or a design pipeline.

Pros
  • +Queue-based batch optimization keeps large image folders manageable
  • +Lossless results preserve pixel data while reducing file size
  • +Command-line interface supports automation in scripts and pipelines
  • +Built-in format handling covers common graphics workflows
Cons
  • –macOS-first workflow limits coverage for Windows and Linux users
  • –Lossless gains depend on encoder choice and source image characteristics
  • –Integration with non-macOS toolchains requires wrappers and scripting
  • –Throughput can drop on very large batches without queue tuning
Use scenarios
  • Privacy-conscious photographers

    Strip metadata while compressing photos

    Lean image files

  • Content and marketing teams

    Preprocess images for CMS imports

    Reduced upload sizes

Show 2 more scenarios
  • Design operations teams

    Apply repeatable folder compression rules

    Space-efficient archives

    Teams compress existing asset libraries in batches using consistent image handling and metadata rules.

  • Creative teams and designers

    Compress exported PNG and JPEG folders

    Lighter production graphics

    Designers optimize export folders before handoff so production assets need less rework.

Best for: Fits when a macOS workflow needs lossless PNG and related re-encodes in repeatable batch jobs.

#2

NX Power Lite Desktop

enterprise

Desktop file compression software that reduces Office, PDF, and image file sizes without changing format.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Content-aware lossless preprocessing that selects per-format packing behavior and verifies integrity per run.

NX Power Lite Desktop targets lossless size reduction by applying format-specific preprocessing and packing decisions per file, rather than treating every input the same. The desktop workflow handles selection, output naming, and batch settings in one place, while the CLI enables unattended compression for scripted pipelines. Compression results include size deltas and integrity checks to help operators confirm no corruption occurred during processing.

A key tradeoff is that format compatibility depends on which input types NX Power Lite can preprocess, so uncommon file formats may compress less or be skipped. NX Power Lite fits best when shared drives and incoming attachments need consistent batch compression before posting to storage, email systems, or document portals.

Pros
  • +Lossless compression with integrity verification output for batch jobs
  • +File and folder batch processing with consistent output naming
  • +Desktop workflow paired with a command-line interface for automation
  • +Format-aware preprocessing decisions to avoid generic archive wrappers
Cons
  • –Coverage of uncommon file types is narrower than general-purpose archivers
  • –Queue-level control is limited compared with toolchains that expose per-file tuning
Use scenarios
  • IT operations teams

    Reduce shared-drive storage for attachments

    Lower storage use without corruption risk

  • Creative asset managers

    Shrink PNG and metadata-heavy exports

    Smaller exports for review pipelines

Show 2 more scenarios
  • Automation engineers

    Run scripted compression jobs

    Hands-off reduction during batch windows

    Uses the command-line interface to compress directories during scheduled processing runs.

  • Document management teams

    Prepare files for document portals

    Faster uploads and less storage overhead

    Compresses mixed office and archive inputs and reports size deltas per run.

Best for: Fits when teams need repeatable lossless compression for mixed file folders.

#3

Squoosh

vertical specialist

Squoosh is a browser-based image compressor with lossless and lossy codec controls.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Side-by-side encode and size comparison built for interactive, per-asset testing in the browser.

Squoosh is a browser-based lossless compression workbench that focuses on visual, per-file testing rather than batch-first workflows. It lets users run codec engines on individual assets, compare outputs, and download results while keeping source integrity checks in view.

The core capability is image-centric encoding with a repeatable try-and-compare loop for formats like PNG and WebP. It also supports archive workflows like creating compressed bundles from selected files.

Pros
  • +Browser UI shows side-by-side results for lossless image experiments
  • +Format-focused engine support covers common image pipelines
  • +Quick export flow for converting individual files without local setup
  • +Deterministic test loop for comparing output size across attempts
Cons
  • –Lossless archive workflows are limited compared with dedicated archivers
  • –Automation is thin since there is no first-class CLI or daemon interface
  • –No built-in RBAC or org-level audit log for shared workspaces
  • –Large-file throughput suffers versus native compression tools
Use scenarios
  • Editors and developers

    Test image artifacts with previews

    Better compression decisions

  • Web publishers and editors

    Tune JPEG quality against the source

    Controlled output quality

Show 2 more scenarios
  • Web designers and front-end developers

    Tune and validate web image exports

    Web-ready assets

    Developers run per-file codec experiments to choose a size and appearance balance for publishing.

  • Photographers and image editors

    Optimize one photo with save confirmation

    Individually tuned output

    Photographers tune settings for a single image and visually confirm the result before writing output.

Best for: Fits when image files need quick lossless size comparisons without installing compression software.

#4

Keka

SMB

macOS archive utility for 7z, ZIP, TAR, and related lossless compression formats.

8.4/10
Overall
Features8.4/10
Ease of Use8.3/10
Value8.5/10
Standout feature

Solid archive controls and file splitting are exposed in the same workflow for build and release packaging.

Keka fits teams that need consistent archive creation across multiple operating systems and that want predictable output settings. Compression behavior is controlled through exposed options like method selection, compression level, and solid archive settings where supported by the target format.

Pros
  • +Cross-OS workflow for consistent archive settings
  • +GUI options include solid archive toggles and compression levels
  • +CLI support helps batch jobs and scripted pipelines
  • +File splitting supports large artifacts without external tooling
Cons
  • –Advanced format tuning is less granular than specialized archivers
  • –Some niche codecs and edge-case compatibility require format-specific handling
Use scenarios
  • Build and release engineers

    Package build artifacts with repeatable settings

    Fewer rework iterations per release

  • System administrators

    Run batch compression for log retention

    Lower storage usage for logs

Show 1 more scenario
  • QA teams

    Archive test sets for artifact sharing

    Reliable artifact exchange

    Split large datasets into chunks to match transfer limits while keeping lossless integrity.

Best for: Fits when teams need repeatable, cross-platform lossless archives with batch automation.

#5

libarchive

API-first

libarchive is a portable C library and command-line toolkit for reading and writing archive formats.

8.2/10
Overall
Features8.2/10
Ease of Use8.1/10
Value8.3/10
Standout feature

libarchive offers a unified reader and writer API that normalizes many archive formats under one processing model.

libarchive is a lossless compression and archival library with a CLI front-end, which differentiates it from GUI-first compression tools. It provides format-agnostic archiving and extraction across many container and archive types, using a consistent API surface for reading and writing.

Pros
  • +Format-agnostic extraction and creation across many archive container types
  • +Streaming-oriented design suitable for pipelines and large archives
  • +Library API enables consistent automation beyond the CLI
  • +Checksum integrity support helps detect corruption during processing
Cons
  • –CLI workflows can be less discoverable than GUI drag-and-drop tools
  • –Advanced codec tuning is limited compared with specialist archivers
  • –Cross-format compatibility depends on the specific input archive type
  • –Complex batch jobs require scripting to match GUI convenience
Use scenarios
  • Build and release engineers

    Stream compress artifacts with retries

    Fewer corrupted artifacts

  • Data engineering pipelines teams

    Extract multiple archive types in one job

    Less workflow branching

Show 1 more scenario
  • Systems integrators and toolmakers

    Embed archive logic into apps

    Predictable automation behavior

    Application code can reuse libarchive’s consistent API for reading and writing archives with integrity controls.

Best for: Fits when automation pipelines need streaming-safe, lossless archive handling on Windows, Linux, or macOS.

#6

B1 Archiver

SMB

B1 Archiver creates and extracts archives across major desktop operating systems.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Built-in checksum validation tied to archive operations reduces silent corruption risk in handoffs.

B1 Archiver targets Windows users who need lossless archive creation with a file-first workflow and a clear separation between compression settings and output formats. It supports common archive formats, provides an Explorer-style UI, and also offers a command-line interface for batch jobs.

Pros
  • +Explorer-style UI makes selecting files, exclusions, and destinations straightforward
  • +Batch-friendly CLI supports folder-driven runs and scripted repeatability
  • +Integrity checks help catch corruption after unpacking and transfers
  • +Compression level controls make it easier to trade size for speed during builds
Cons
  • –Advanced codec and tuning depth stays limited versus specialist compressors
  • –Large archives with many small files can show weaker throughput than low-level tools
Use scenarios
  • Freelancers and small teams

    Create compact delivery archives

    Easier sharing

  • Users with transfer limits

    Assemble multipart archives after upload

    Completed transfers

Show 2 more scenarios
  • Support teams and file admins

    Repackage selected content into new archives

    More usable packages

    Admins browse an existing archive, select content, and create a new package in a more practical format.

  • Teams exchanging large collections

    Validate archives during transfer

    Earlier integrity failures

    Integrity checks help identify corruption before transferred files are used in downstream workflows.

Best for: Fits when desktop teams want a simple UI plus CLI scripting for lossless archive delivery.

#7

NanaZip

SMB

NanaZip is a Windows archive manager with modern shell integration and 7-Zip format support.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

Command-line batch archiving is designed to mirror the GUI workflow for predictable automation runs.

NanaZip is a lossless compression app built around modern archiving defaults and a focus on Windows-first usability. It provides a GUI that drives a consistent set of archive formats and compression options for everyday compression and extraction workflows.

Pros
  • +GUI and CLI share the same archive workflow for consistent results
  • +Good defaults for common lossless formats without extra tuning
  • +Fast extraction and archive creation for small to medium file sets
  • +Supports batch usage through command-line scripting
Cons
  • –Advanced per-file and per-stream tuning is thinner than top-tier archivers
  • –Codec and format coverage lags behind tools with the broadest compatibility
Use scenarios
  • Windows file managers

    Compress folders via drag-and-drop

    Quick lossless archives

  • QA and release coordinators

    Batch archive assets with CLI

    Repeatable packaging

Show 1 more scenario
  • IT support teams

    Extract and repackage support bundles

    Fewer packaging errors

    Support teams use the GUI and CLI to move between archive formats without losing data from lossless operations.

Best for: Fits when Windows users need a clean GUI plus scripting for frequent lossless archives.

#8

GNU gzip

developer

GNU gzip provides command-line DEFLATE compression and decompression for Unix-like systems.

7.1/10
Overall
Features7.1/10
Ease of Use7.0/10
Value7.2/10
Standout feature

Header-stored original filename and metadata plus CRC and input size checks support integrity-aware streaming pipelines.

GNU gzip compresses and decompresses files using the DEFLATE coding used by the gzip file format. It provides a predictable CLI workflow, supports streaming to standard input and output, and preserves file metadata with the original name stored in the header.

Pros
  • +Streaming-friendly CLI supports piping without temporary files
  • +CRC and uncompressed size checks add integrity verification
  • +Widely interoperable gzip format for cross-platform transfers
  • +Simple flags make scripted batch compression straightforward
Cons
  • –Compression ratio can lag modern codecs like Zstandard
  • –No archive container layer for multiple files compared to tar-based workflows
  • –Limited tuning options beyond compression level and basic metadata handling
  • –Not optimized for very large in-memory datasets due to process-based usage
Use scenarios
  • DevOps operations teams

    Compress and stream logs through pipelines

    Lower transfer size

  • Site reliability engineers

    Decompress data with integrity checks

    Fewer bad restores

Show 1 more scenario
  • Software release teams

    Package single text artifacts with gzip

    Consistent artifact handling

    Teams compress common text or log files using DEFLATE for predictable interoperability with existing tooling.

Best for: Fits when teams need lossless, scriptable compression compatible with standard gzip tooling.

#9

Express Zip

SMB

File compression and archiving software for creating and extracting lossless compressed archives.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

GUI-first archive workflow with compression level controls and CLI support for the same packaging steps.

Express Zip is geared toward desktop users who want frequent archive operations without switching between multiple utilities. It handles typical archive workflows such as creating, extracting, and editing archives while keeping file selection and destination paths in a predictable sequence. Compression settings such as level control allow tradeoffs between size and time for tasks like compressing large document folders.

Pros
  • +Windows-focused archive UI reduces context switching for daily packaging work
  • +Compression level controls allow size versus time tuning per job
  • +Works well for batch archive creation with repeatable selection patterns
  • +Command-line usage supports scripted packaging outside the GUI
Cons
  • –Limited admin and governance controls compared with enterprise archivers
  • –Automation surface is more CLI-centric than API-centric
Use scenarios
  • IT support teams

    Pack collected logs for tickets

    Smaller attachments for handoff

  • QA teams

    Ship test artifacts as archives

    Faster internal distribution

Show 2 more scenarios
  • Operations coordinators

    Bundle export folders for vendors

    Reduced transfer volume

    Package export folders into compressed files to reduce download friction.

  • Power users

    Automate archive creation from scripts

    Repeatable batch packaging

    Use command-line runs to package folders consistently across schedules.

Best for: Fits when Windows teams need quick, repeatable archive packaging for file transfers and internal handoffs.

#10

XZ Utils

developer

XZ Utils provides LZMA2-based compression through command-line tools and library components.

6.6/10
Overall
Features6.6/10
Ease of Use6.7/10
Value6.5/10
Standout feature

Dictionary size and preset tuning for the XZ encoder, paired with checksum verification, enables tight control over compression ratio versus resource use.

XZ Utils provides lossless compression and decompression for XZ, LZMA, and legacy formats using the command line tools xz and lzma. The toolset includes encoder controls for compression level, preset selection, dictionary sizing, and integrity checks using CRC32.

Pros
  • +Strong XZ encoder controls for presets, dictionary size, and threading
  • +Built-in integrity checking for XZ streams with clear failure modes
  • +Stable CLI workflow suitable for automation and batch archives
  • +Minimal external dependencies for common compression and extraction
Cons
  • –No built-in archive manager interface for multi-format workflows
  • –Advanced tuning like dictionary size can increase memory pressure
  • –Feature set is narrow versus tools that integrate many archive formats
  • –Windows and macOS use depends on packaging rather than a unified experience
Use scenarios
  • Build and packaging engineers

    Tune XZ compression presets for distribution

    Smaller distributions

  • Release automation teams

    Script decompression with strict exit codes

    More reliable automation

Show 1 more scenario
  • Linux administrators

    Verify integrity of downloaded archives

    Earlier corruption detection

    Checksum verification using CRC32 helps confirm archived content before it is used.

Best for: Fits when automated CLI compression of XZ and LZMA streams matters more than GUI workflows.

Conclusion

After evaluating 10 lossless compression software, ImageOptim stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
ImageOptim

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Lossless Compression Software

How does NX Power Lite Desktop preserve lossless integrity for mixed folders?
NX Power Lite Desktop applies content-aware lossless preprocessing per file type and reports before-and-after sizes for each run. It also validates checksum integrity so teams can confirm the output is lossless after the batch completes.
Which tool is better for lossless batch archives across Windows, macOS, and Linux?
Keka targets Windows, macOS, and Linux with a single workflow that covers compression level tuning and file splitting. NanaZip also offers Windows GUI plus CLI batch runs, but it does not provide the same cross-platform coverage as Keka.
When should a team choose libarchive over GUI-first archivers?
libarchive fits pipelines that require a unified reader and writer API across many archive formats under one processing model. It supports automation via a CLI front-end and per-entry handling that emphasizes predictable streaming-safe behavior.
What breaks if XZ Utils is configured with aggressive dictionary sizing in automation?
Aggressive dictionary size and preset choices in XZ Utils can raise memory footprint during encoding, which can stall throughput in constrained CI runners. XZ Utils still performs CRC32 integrity checks, but resource pressure can become the limiting factor before compression completes.
How do XZ Utils and GNU gzip differ for streaming lossless compression in scripts?
GNU gzip supports streaming to standard input and output and validates integrity using a stored CRC plus input size checks. XZ Utils is built around xz and lzma encoding with preset and dictionary controls, which makes it more suited to streamable workflows where the encoder can hold its working state.
Which tool provides a tight GUI-to-CLI workflow match on Windows?
NanaZip is built so the command-line batch behavior mirrors the drag-and-drop GUI workflow for consistent automation. Express Zip also pairs a GUI workflow with command-line usage patterns, but NanaZip focuses on mirroring daily archive steps more directly.
What tradeoff appears when using solid-archive style packaging in Keka for large transfers?
Keka exposes archive controls plus file splitting in the same workflow, which helps keep transfer units manageable. Large solid archives can reduce random-access and partial extraction flexibility, so split sizing and archive layout become the operational tradeoff.
How does ImageOptim ensure lossless image results while batch processing PNG assets?
ImageOptim re-encodes images without changing visible pixels, and its macOS-first queue workflow batches repeated optimizations consistently. Squoosh offers interactive per-asset comparisons in the browser, but it is less automation-oriented than ImageOptim’s queue-based pipeline.
Where does Squoosh fall short compared with desktop archivers when building compressed bundles from many files?
Squoosh is optimized for a try-and-compare loop on individual assets with side-by-side size and codec outputs. Express Zip and Keka focus on repeated archive packaging steps for folder transfers, so Squoosh typically adds extra interaction for large multi-file bundle workflows.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Lossless Compression Software

Lossless compression software differs most in how it handles your data at scale: whether it preserves byte-for-byte originals, how reliably it automates jobs, and how transparent it is when diagnosing failures. The biggest gaps show up in criteria like lossless verification, automation hooks, and recovery from partial runs.

Lossless verification and integrity checks

Why it matters

Lossless verification and integrity checks matter because a “successful” run can still produce output that fails strict round-trip comparisons. If the tool can’t prove correctness, you may discover issues only after files propagate through your workflow.

How to check

Pick a small set of mixed files that include text, binaries, and already-compressed formats you care about. Compress, decompress, then run a byte-for-byte comparison (or use the tool’s own verification option) and document whether it reports pass/fail.

Job automation and scheduling control

Why it matters

Job automation and scheduling control matters when compression is part of recurring processing, backup prep, or media archiving. The tool needs predictable, repeatable runs rather than manual steps.

How to check

Ask for an example workflow: compress a folder, preserve structure, and decompress to a new location. Verify that the same configuration can be executed unattended (for example via documented scripts or scheduler-friendly command steps) and that exit status meaningfully indicates success or failure.

File format and archive layout options

Why it matters

File format and archive layout options determine portability and how you recover data later. Choices around container structure and metadata can affect compatibility with other systems and how quickly you can extract specific items.

How to check

Request a demo using two different output modes (if offered): one that groups files together and one that keeps entries separately. Then test extraction of a single item without fully expanding everything else, and note whether metadata (paths, timestamps) is preserved the way you need.

Throughput controls and resource limits

Why it matters

Throughput controls and resource limits matter because lossless compression can be CPU- or memory-bound. If you can’t cap resources, runs may interrupt other business workloads or make batch timelines unpredictable.

How to check

Run the same dataset twice while changing available settings that target speed vs resource use. Record whether the tool exposes adjustable limits (thread count or similar) and whether results remain deterministic in integrity checks after tuning.

Random access and extraction behavior

Why it matters

Random access and extraction behavior matters when you need to retrieve a subset of compressed content quickly. If decompression forces full rebuilds, you’ll pay extra time and operational risk.

How to check

After creating an archive, extract one file near the middle (not the first). Measure whether the tool can locate and decode only what’s needed, and confirm that integrity checks still run cleanly for the extracted file.

Red flags

  • Runs that lack a verifiable round-trip comparison for byte-level correctness.
  • Automation that requires manual prompts or non-deterministic steps.
  • Archive outputs that make partial extraction slow or unreliable.

Fit by situation

  • If you handle regulated or audit-sensitive archives, prioritize lossless verification and integrity checks.
  • If compression runs nightly or on-demand, prioritize job automation and scheduling control.
  • If teams need to retrieve only a subset of stored items, prioritize random access and extraction behavior.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.