GITNUXSOFTWARE ADVICE
Art DesignTop 10 Best Reviews Photo Editing Software of 2026
Ranked Reviews Photo Editing Software picks with technical notes and tradeoffs for photographers, including Photoshop, Affinity Photo, and Capture One.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Adobe Photoshop
Smart Objects preserve source edits while allowing nondestructive transforms across workflows.
Built for fits when creative teams need governed PSD structure and repeatable automation..
Affinity Photo
Editor pickNon-destructive layer stack with masks and adjustment layers for repeatable edits.
Built for fits when teams need local, file-driven photo automation without admin governance features..
Capture One
Editor pickCatalog-driven non-destructive adjustments with styles and batch reapplication across assets.
Built for fits when mid-size studios need controlled RAW workflows with automation and role governance..
Related reading
Comparison Table
The comparison table maps photo editing tools by integration depth, including host application workflows and how each product exposes automation and API surface. It also compares data model and schema design for catalogs, presets, and edits, plus extensibility options like plugins and scripting. Admin and governance controls are covered through RBAC and audit log support to show how teams can provision access and track changes at scale.
Adobe Photoshop
desktop editorDesktop image editor with scriptable automation via JavaScript and a file format workflow for review-ready photo revisions.
Smart Objects preserve source edits while allowing nondestructive transforms across workflows.
Adobe Photoshop provides a structured data model through layers, smart objects, adjustment layers, and masks stored inside PSD files, which keeps edits replayable. It includes color management features like ICC profiles and soft-proofing, and it handles high dynamic range workflows via 32-bit formats in supported paths. Extensibility covers UXP extensions and traditional script automation, which enables repeatable transforms like batch retouching, channel operations, and template-based exports.
A concrete tradeoff is that Photoshop automation is tightly bound to document structure, so scripts require consistent layer naming, group topology, and adjustment wiring to prevent brittle failures. Teams using visual QA and production retouching benefit most when PSD templates define a stable schema for layers and smart object slots, then automated exports feed downstream channels.
- +Non-destructive layers, masks, and smart objects keep edits editable in PSD
- +Color management with ICC handling and soft-proofing supports print and display parity
- +Automation via ExtendScript and extensibility via UXP enable repeatable pipelines
- –Script reliability depends on consistent layer and adjustment structure
- –High-throughput batch work needs careful document normalization and hardware planning
Production retouch teams
Batch export from standardized PSD templates
Higher throughput with fewer rework cycles
Brand and marketing operations
Color-managed asset refresh across channels
More consistent color output
Show 2 more scenarios
Creative engineering teams
Build internal Photoshop automation tooling
More automation with less manual editing
Uses scripting hooks and UXP extensibility to connect document operations to broader asset workflows.
Agencies with shared deliverable specs
Template-driven edits for multiple clients
Faster approvals with fewer inconsistencies
Relies on PSD structure and reusable layer setups to reduce variance between retouchers.
Best for: Fits when creative teams need governed PSD structure and repeatable automation.
More related reading
Affinity Photo
desktop editorDesktop photo editor with batch processing and automation-friendly design-time workflows for iterative review edits.
Non-destructive layer stack with masks and adjustment layers for repeatable edits.
Affinity Photo fits teams that treat image assets as local, file-backed records and want predictable throughput in a managed workstation environment. It supports layered editing with adjustment layers and masking, plus raw development that feeds the same layer stack. Automation exists through batch processing and extensibility points, but it does not offer a rich admin RBAC or centralized audit log for multi-user governance.
A key tradeoff appears when workflows depend on server-side orchestration, external CM systems, or strict admin controls. Affinity Photo works well when a single artist or small team needs repeatable production edits and can standardize configuration per workstation.
- +Layer and mask workflow supports non-destructive retouching
- –Limited integration depth for external asset platforms and schemas
Independent retouchers
Batch edits for product catalogs
Faster production iterations
Small creative teams
Raw-to-layer compositing for campaigns
More consistent exports
Show 1 more scenario
Production managers
Workstation-based QA for retouch sets
Lower rework rate
Layer history and configuration reuse support repeatable review checkpoints per file.
Best for: Fits when teams need local, file-driven photo automation without admin governance features.
Capture One
raw workflowRaw processing and catalog workflow for review stages with automation through tethering and batch processing capabilities.
Catalog-driven non-destructive adjustments with styles and batch reapplication across assets.
Capture One builds a data model that keeps edits attached to assets through catalogs, collections, and adjustment settings that can be reapplied without overwriting source data. The product supports extensibility through APIs for workflow automation, plus programmatic access patterns for color and asset management tasks that fit custom pipelines. Tethered capture and batch workflows increase throughput when shoots feed predictable naming and ingest conventions.
A key tradeoff is that advanced automation and governance depend on how catalogs and projects map to team roles and storage layout, which can require careful provisioning before scaling. Capture One fits best when photo teams need repeatable development presets and scripted batch steps across multiple cameras while maintaining audit-ready change history through adjustment versions.
- +Non-destructive edits stay tied to assets through a structured catalog model
- +Tethered capture supports consistent ingest into projects for live production workflows
- +API and automation surface supports repeatable recipes and scripted batch processing
- +Role-based access and project organization support team governance
- +Styles and presets enable consistent looks across sessions and batches
- –Automation design hinges on catalog and project mapping to storage structure
- –Extensibility requires engineering effort for custom workflows
- –Large libraries can increase configuration and maintenance overhead
Photo studio production teams
Tether shoots into governed projects
Faster client review cycles
Post-production workflow engineers
Automate batch development steps
Higher throughput with fewer errors
Show 2 more scenarios
Creative ops teams
Standardize looks across photographers
Uniform results across projects
Styles and presets enforce consistent color and development settings.
Media asset managers
Maintain schema-like organization
Predictable reprocessing later
Catalog structures provide a stable data model for metadata and adjustments.
Best for: Fits when mid-size studios need controlled RAW workflows with automation and role governance.
Luminar Neo
desktop editorDesktop photo editor that generates review-ready edits with guided workflows and batch processing for consistent output.
AI sky replacement with mask-aware compositing for fast background changes.
In photo editing software reviews, Luminar Neo is a creative-first editor built around AI-assisted tools and a strong non-destructive workflow. Core capabilities include layered editing, RAW support, preset-based looks, and AI features like sky replacement and subject relighting.
Integration depth is limited to media import and export paths rather than a documented editing API or workflow orchestration layer. Automation and governance controls focus on local configuration and project management rather than RBAC, audit logs, or admin-driven provisioning.
- +Layer-based non-destructive editing with project-friendly history
- +AI-assisted tools for sky replacement and object edits
- +Preset and mask workflows reduce repeat effort across images
- +RAW handling with color and tone controls for consistent outputs
- –No documented public API for programmatic editing or batch pipelines
- –No RBAC, admin provisioning, or audit log controls for teams
- –Automation relies on local workflows rather than external orchestration
- –Integration depth stays within file-based import and export
Best for: Fits when individuals or small teams need AI editing with local repeatable presets.
ON1 Photo RAW
desktop editorPhoto editing suite with batch edits and a workflow oriented around producing consistent review exports from cataloged images.
Layer-based non-destructive editing with persistent raw processing parameters
ON1 Photo RAW performs raw conversion, non-destructive editing, and layered photo workflows inside one desktop app. Its editing data model includes adjustable processing controls for raw, lens corrections, and effect layers that persist across export.
Batch processing supports repeatable pipelines for throughput across large libraries. Extensibility and automation rely primarily on presets and scripting adjacent workflows rather than a documented external API surface.
- +Non-destructive layer stack preserves edit parameters through export
- +Raw conversion includes lens corrections and noise controls per image
- +Batch processing supports repeatable adjustments across folders
- +Presets capture processing configuration for consistent throughput
- +Catalog-style organization supports search over large photo sets
- –Automation depends on presets and manual batch triggers
- –External API surface for provisioning and integration is not a primary model
- –RBAC and audit log controls are not designed for admin governance
- –Cross-system workflow integration depth is limited to file-based handoffs
- –Automation extensibility is constrained compared to API-first tools
Best for: Fits when photographers need configurable raw and layer edits without heavy system integration.
GIMP
open-source editorOpen-source raster editor with automation via Script-Fu and batch processing for repeatable review pipelines.
Script-Fu and plug-in architecture enable custom image processing pipelines.
GIMP fits teams and individuals needing an on-device photo editor with scripting and plugin extensibility. Its core workflow covers layers, masks, non-destructive adjustments via layer structure, and wide format import and export.
Automation relies on built-in scripting and external batch processing hooks rather than a centralized asset schema. Integration depth remains mostly local to the desktop and filesystem, with limited admin and governance surfaces.
- +Layer and mask workflow supports complex edit compositions
- +Scripting and plug-ins extend tools without rewriting the editor
- +Batch processing enables repeatable operations across many files
- +Cross-platform desktop deployment supports mixed OS environments
- –Limited automation and API surface for external systems
- –No built-in RBAC, audit log, or admin governance controls
- –Asset metadata model and schema tooling are minimal
- –Automation often depends on local file conventions
Best for: Fits when teams need desktop photo automation through scripts and plugins, not centralized governance.
Darktable
open-source rawOpen-source raw developer and non-destructive editing tool with batch workflows for review batches and repeatable exports.
Lighttable and Darkroom modules drive a parametric editing stack stored in the processing history.
Darktable distinguishes itself with a non-destructive, metadata-first editing workflow that writes adjustments as sidecar-style processing history. Edits are organized through a parametric data model tied to import and processing modules, which keeps raw pixel data immutable.
Automation is largely file-centric through command-line batch processing and scripted render pipelines rather than a network API. Integration depth is strongest with local filesystem conventions and export pipelines, with extensibility achieved via plugin mechanisms instead of external services.
- +Non-destructive pipeline stores edits as module parameters, not destructive pixel rewrites
- +Parametric workflow enables consistent re-rendering when module settings change
- +Command-line batch processing supports scripted throughput for large import sets
- +Metadata and sidecar-like storage keep editing history portable across sessions
- +Plugin architecture adds processing modules and extends the editing graph
- –No documented network API limits programmatic control and remote orchestration
- –Automation surface centers on CLI export rather than interactive workflow triggers
- –Admin and governance controls like RBAC and audit logs are not designed for teams
- –Thumbnails, cache, and render behavior can add operational complexity at scale
- –Cross-system coordination depends on filesystem access patterns and metadata portability
Best for: Fits when single-user or small workflows need non-destructive editing and batch exports.
RawTherapee
open-source rawOpen-source raw processor with batch queue processing for production of consistent review-ready renders.
Advanced demosaic controls with detailed sharpening and noise reduction stages in one render pipeline
RawTherapee is a desktop-focused RAW photo editor centered on non-destructive processing workflows. It supports an extensive processing pipeline with detailed demosaic, lens correction, noise reduction, sharpening, and color management controls.
Output can be standardized through render presets and batch processing. Integration depth is limited because RawTherapee does not provide an external API for automation or provisioning.
- +Fine-grained RAW processing controls across demosaic, denoise, and sharpening stages
- +Batch processing supports preset-driven throughput for large import sets
- +Non-destructive workflow keeps edits reversible within exported render outputs
- +Lens correction and color pipeline options support repeatable camera-specific rendering
- –No documented API surface for external automation or integration
- –Limited administration and governance controls for multi-user environments
- –Automation is confined to built-in batch and presets without external scheduling hooks
- –Data model exports are file-based without schema or audit log support
Best for: Fits when individual photographers need deterministic RAW rendering without external workflow systems.
ImageMagick
automation toolkitCommand-line image processing toolkit with scripting and automation for review generation using reproducible transforms.
Unified command-line and API processing model using a single, consistent operation and option system.
ImageMagick converts, edits, and composes images through a command-line toolchain and library APIs. ImageMagick supports an extensive feature set for format handling, pixel-level operations, and batch workflows using a consistent image processing data model.
ImageMagick integrates into automation via CLI scripting and programming bindings that expose options, filters, and pipelines. Automation depth is driven by its deterministic command arguments and scriptable processing graphs rather than a centralized admin interface.
- +CLI-driven processing supports batch throughput and reproducible image pipelines
- +Library APIs expose the same transformation model used by command execution
- +Rich format and codec support covers many ingest and export workflows
- +Extensible operators and filters enable custom processing steps
- –No native RBAC or multi-tenant governance controls for shared environments
- –Audit logging and approvals are not part of a built-in workflow system
- –Complex command arguments increase configuration error risk at scale
- –Sandboxing and policy controls are limited compared to managed services
Best for: Fits when engineering teams need configurable image automation with minimal external orchestration overhead.
OpenCV
vision automationComputer vision library used to automate photo edits with scripted transforms and measurable image operations in pipelines.
Extensible module architecture with operator registration for adding custom processing stages.
OpenCV fits teams that need repeatable, code-driven image and video processing inside existing pipelines. Core capabilities include classical computer vision operations like filtering, feature detection, camera calibration, and geometric transforms.
The data model is based on explicit matrix and tensor-like image representations that make data flow and memory behavior predictable across operators. Integration depth comes from language bindings and a large, well-documented API surface for automation, extensibility, and throughput-oriented batch processing.
- +Language bindings for C++, Python, and Java support pipeline integration
- +Explicit image matrix data model clarifies schema-like operator contracts
- +Wide algorithm coverage spans filtering, transforms, and calibration workflows
- +Composable API enables automation via scripts and custom processing graphs
- +Extensible module system allows adding and registering specialized operators
- –No built-in RBAC, audit logs, or admin governance for shared environments
- –Admin controls require external orchestration and process-level permissions
- –Limited first-party photo editor UX for interactive retouching workflows
- –Automation requires engineering effort to build reliable batch pipelines
- –Throughput tuning depends on correct build options and memory management
Best for: Fits when teams need code-level image processing automation with direct control over data flow.
How to Choose the Right Reviews Photo Editing Software
This buyer's guide covers desktop and automation-oriented photo editing tools used to produce review-ready image revisions, including Adobe Photoshop, Capture One, Affinity Photo, and open-source editors like GIMP and Darktable.
The guide focuses on integration depth, data model design, automation and API surface, and admin and governance controls that shape repeatability at scale. It also compares local-file workflows like Luminar Neo and ON1 Photo RAW with code-driven pipelines in ImageMagick and OpenCV.
Tools used to generate review-ready photo revisions with repeatable edits, exports, and processing history
Reviews photo editing software is used to create, adjust, and re-export images so downstream reviewers get consistent output across batches, projects, and revisions. These tools solve problems like non-destructive edit retention, repeatable RAW conversion, and standardized export behavior for large image sets.
Adobe Photoshop and Capture One show how non-destructive workflows and structured models support iterative review stages. Luminar Neo and ON1 Photo RAW show how guided preset-driven output supports consistency without heavy external orchestration.
Evaluation criteria for integration, data model control, and automation surfaces
Integration depth determines whether edits and metadata can participate in an external workflow through files only or through a documented automation surface. Data model quality determines whether edits remain editable across sessions and how reliably edits can be re-applied to new assets.
Automation and API surface controls how repeatable processing becomes for large throughput. Admin and governance controls determine whether teams get role-based access and traceability via audit logging and permissions models.
Non-destructive edit preservation with structured edit containers
Adobe Photoshop keeps edits editable through non-destructive layer stacks, masks, and Smart Objects stored in PSD structures. Affinity Photo also emphasizes a layer and mask workflow with adjustment layers for repeatable retouching that stays reversible inside the editing session.
Catalog-driven RAW and adjustment models for reapplication
Capture One organizes non-destructive RAW development through a catalog-aware data model tied to metadata and adjustments. This enables batch reapplication of styles and presets across assets while keeping edits tied to the same structured project model.
Documented automation and API or SDK surfaces for programmatic workflows
Adobe Photoshop offers scripting through ExtendScript and extensibility via Adobe UXP and plugin frameworks for repeatable pipelines. Capture One provides an automation surface that includes API and SDK access patterns for scripted batch processing and workflow extension.
Batch processing that preserves configuration across many assets
Capture One uses styles and repeatable recipes to apply consistent looks across batches within its catalog structure. ON1 Photo RAW uses presets to capture processing configuration and then applies them across folders for throughput across large libraries.
Admin and governance controls for teams using shared libraries
Capture One includes role-based access and project organization to support team governance across structured workflows. Photoshop can be governed through controlled PSD structure and repeatable automation patterns, while tools like Luminar Neo lack RBAC, audit logs, and admin provisioning controls.
Integration approach based on files versus network orchestration
Luminar Neo and RawTherapee focus on local import and export paths and do not provide a documented editing API for orchestration. Darktable and GIMP also center automation on local workflows such as command-line batch processing or scripting rather than network-based admin-managed integrations.
A decision framework for matching photo edit workflows to automation and governance needs
The selection process starts by mapping required edit persistence, then moves to automation depth and control boundaries. The right tool depends on whether the organization needs governed asset models and scripted pipelines or mostly local file-driven repeatability.
Each step below ties tool capabilities to concrete decision points so the final selection matches how review revisions actually get generated and re-generated.
Define the edit persistence contract and the required data container
If review revisions must stay editable as layers and transforms, Adobe Photoshop and Affinity Photo fit because they keep non-destructive layer stacks, masks, and adjustment structures. If the workflow must stay tied to RAW development parameters and metadata over time, Capture One fits because its catalog-driven model keeps non-destructive adjustments linked to assets.
Choose a data model strategy for large libraries and repeat re-rendering
If consistent looks need to be re-applied across many images with a managed project structure, Capture One uses styles and presets across cataloged assets. If the project can rely on a persistent processing history stored as module parameters, Darktable provides a parametric editing stack stored in the processing history for consistent re-rendering.
Match automation requirements to the available API or scripting surface
For organizations needing scripted pipelines integrated into an existing environment, Adobe Photoshop scripting via ExtendScript and Capture One automation via API and SDK access patterns support repeatable batch work. If the automation target is engineering pipelines rather than interactive retouching, ImageMagick provides a unified command-line and library API model and OpenCV provides a code-first operator API for custom processing graphs.
Set governance requirements for access control and traceability
For team environments that require role-based access and permissioned projects, Capture One provides role-based access tied to project organization. If governance must include RBAC and audit log controls, Luminar Neo and ON1 Photo RAW do not focus on those admin features, while ImageMagick and OpenCV also do not include built-in multi-tenant governance layers.
Decide whether orchestration is file-based or network-managed
For workflows that can operate on filesystem inputs and standard exports, Darktable and RawTherapee support command-line batch exports and preset-driven rendering with local processing history. For workflows that need external orchestration beyond file import and export, prefer tools with documented automation or SDK surfaces like Adobe Photoshop and Capture One, or code libraries like OpenCV.
Which teams and workflows fit each photo edit automation and governance profile
Different tools match different operational constraints around repeatability, control, and how edits flow between systems. The best selection depends on whether governance and integration require a managed data model or can remain local.
The segments below map to the specific best-for profiles from the reviewed tools.
Creative teams that must keep governed PSD structure and repeatable scripted edits
Adobe Photoshop fits when teams need governed PSD structure and repeatable automation. Smart Objects preserve source edits while enabling nondestructive transforms across workflows.
Mid-size studios that need controlled RAW workflows with role-based governance and batch reapplication
Capture One fits studios that need controlled RAW workflows with automation and role governance. Its catalog-driven data model ties non-destructive adjustments to assets and supports style reapplication and batch recipes.
Individuals and small teams that want AI-assisted review output using local presets
Luminar Neo fits individuals or small teams that want AI sky replacement and mask-aware compositing using local preset workflows. Its automation centers on local repeatable presets rather than RBAC, audit log controls, or a documented public API.
Photographers who need configurable raw and layer edits without heavy system integration
ON1 Photo RAW fits photographers who want non-destructive layer and persistent raw processing parameters with batch exports. Its automation relies on presets and manual batch triggers rather than an admin-managed integration surface.
Engineering teams that need code-driven, measurable transforms inside existing pipelines
OpenCV fits teams that need repeatable, code-driven image operations with explicit matrix and tensor-like data models. ImageMagick fits when teams want CLI-driven and library API automation using a consistent option system for reproducible transforms.
Pitfalls that break review repeatability, governance, and automation runs
Common failures come from mismatching automation expectations to the available API or from assuming all tools provide the same level of governed edit history. Another issue is relying on local conventions when team workflows require permissioned shared projects.
The pitfalls below map directly to the cons seen across the reviewed tools.
Assuming AI or guided presets come with an API-first automation surface
Luminar Neo provides guided AI editing like sky replacement and preset-based consistency, but it does not provide a documented public API for programmatic editing or batch pipelines. Batch consistency that depends on local presets can fail when a team needs orchestration from external systems.
Planning centralized team governance with tools that lack RBAC and audit logs
Luminar Neo, ON1 Photo RAW, GIMP, Darktable, RawTherapee, ImageMagick, and OpenCV do not focus on RBAC, audit log controls, or admin provisioning features for multi-user governance. Capture One is the primary reviewed tool that explicitly supports role-based access and team governance around project structure.
Designing automation around fragile layer structures without normalization
Photoshop ExtendScript reliability depends on consistent layer and adjustment structure, and high-throughput batch work requires careful document normalization. This makes batch automation more error-prone when incoming PSDs vary in layer ordering or adjustment naming conventions.
Treating catalog mapping as optional when batch workflows depend on it
Capture One automation design hinges on catalog and project mapping to storage structure, and large libraries can increase configuration and maintenance overhead. Without stable mapping, style reapplication and scripted batches become harder to keep consistent.
Using file-centric batch automation where an external orchestration surface is required
Darktable automation centers on command-line batch processing and scripted render pipelines rather than a network API. RawTherapee also confines automation to built-in batch and presets without an external API for provisioning, which can block integration into centralized workflow systems.
How We Selected and Ranked These Tools
We evaluated each tool on three scored areas: features, ease of use, and value, with features carrying the most weight and ease of use and value sharing the remaining balance. The overall rating is a weighted average that emphasizes capability coverage for non-destructive workflows, batch repeatability, and automation surfaces because those determine whether review pipelines stay consistent across revisions.
This criteria-based scoring used the provided tool descriptions, standout capabilities, and listed constraints rather than private lab experiments. Adobe Photoshop set the highest bar in capability and workflow repeatability by combining non-destructive layers and Smart Objects with automation via ExtendScript and extensibility via UXP and plugin frameworks, which elevated its features and ease-of-use outcomes together.
Frequently Asked Questions About Reviews Photo Editing Software
Which photo editors support non-destructive workflows with persistent edit histories?
What is the most reliable choice for governed PSD-based production with repeatable automation?
Which tools provide integration via APIs or SDKs for automation beyond local batch processing?
How do catalog or metadata data models change batch editing at scale?
Which editor best fits teams that need role-based access and audit-ready administration controls?
What breaks during data migration when moving an existing edit library between tools?
Which tools support tethered capture and studio workflows with recipe-like repeatability?
Which editor is best when the requirement is a command-line processing pipeline with deterministic arguments?
How do extensibility approaches differ across desktop plug-ins, scripts, and code modules?
Which tools help troubleshoot common issues like inconsistent color management or non-matching exports?
Conclusion
After evaluating 10 art design, Adobe Photoshop 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.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Art Design alternatives
See side-by-side comparisons of art design tools and pick the right one for your stack.
Compare art design tools→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 ListingWHAT 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.