GITNUXSOFTWARE ADVICE
Music And AudioTop 8 Best Music Tag Software of 2026
Top 10 Music Tag Software ranked for tag accuracy and bulk editing. Includes MusicBrainz Picard, beets, TagScanner, and key tradeoffs.
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.
MusicBrainz Picard
Configurable tagging rules that translate MusicBrainz entities into written filename and tag fields.
Built for fits when a team needs controlled local batch tagging aligned to MusicBrainz metadata..
beets
Editor pickPlugin system that extends matching and metadata sources while preserving the core library pipeline.
Built for fits when teams need configurable, repeatable tag automation with API-driven integration..
TagScanner
Editor pickRules-based filename and tag formatting that updates multiple files in batch.
Built for fits when music curators need fast desktop bulk tagging without server automation requirements..
Related reading
Comparison Table
This comparison table evaluates Music Tag software by integration depth, underlying data model, and the automation and API surface each tool exposes for metadata, artwork, and renaming workflows. It also contrasts admin and governance controls such as configuration management, extensibility, RBAC support, and audit log coverage where available, plus how each system handles provisioning and schema mapping for consistent tag throughput.
MusicBrainz Picard
metadata taggingA desktop tagging application that writes MusicBrainz-compatible metadata by matching audio against acoustic and tag sources.
Configurable tagging rules that translate MusicBrainz entities into written filename and tag fields.
MusicBrainz Picard performs acoustic and metadata-based matching to MusicBrainz release data, then writes tags into audio files according to configured rules. Its data model centers on recording and release metadata from MusicBrainz, which lets configuration reference artists, release groups, and track relationships without building custom schema. Automation relies on a rule engine, batch scanning, and plugin points that add or alter matching and tagging behavior. An API surface exists via MusicBrainz services that Picard queries for lookup and entity data, but the core tagging engine runs locally on the client for file I O control.
A tradeoff appears in governance and admin controls, since Picard’s configuration is managed per user or workstation rather than through centralized RBAC, provisioning, or audit logging. This makes it less suitable for enterprises that require governed change tracking across teams and shared processing environments. Picard fits a situation where a small team or individual needs consistent metadata writes across a personal library or a departmental ingestion batch. It also fits workflows where configuration is versioned outside the app and applied during controlled library refresh runs.
- +Local batch processing applies tag rules at high throughput
- +MusicBrainz release lookups drive consistent recording and track mapping
- +Rule-based configuration supports repeatable filename and tag generation
- +Plugin extensibility adds new matching and metadata sources
- –Centralized RBAC, provisioning, and audit log controls are limited
- –Tag governance depends on workstation configuration discipline
- –API and automation surface is less suited for server-side orchestration
Independent music librarians and archivists
Batch-tagging a mixed-collection library from imperfect filenames and inconsistent tags
A searchable archive with consistent artists, albums, track numbers, and filenames for downstream ingestion.
Ripping and local music ingestion workflows
Post-rip normalization during periodic library refresh cycles
Lower manual tagging effort and fewer mismatched album or track structures after each refresh.
Show 2 more scenarios
Small teams with shared tagging standards
Enforcing naming conventions and metadata fields across multiple workstations
Uniform metadata output across team members without custom code.
Picard’s rule configuration can encode the team’s desired schema for filenames and tags and then be replicated across machines. The absence of centralized governance means teams manage configuration distribution and change control outside Picard.
Media operations teams coordinating metadata with MusicBrainz
Aligning local library tags to MusicBrainz entities before publishing or syncing elsewhere
Consistent metadata inputs that support reliable downstream synchronization decisions.
Picard uses MusicBrainz entity lookups to map recordings and release details into file tags. This reduces schema drift when other systems expect MusicBrainz-derived naming and track structure.
Best for: Fits when a team needs controlled local batch tagging aligned to MusicBrainz metadata.
beets
automation-firstAn automation-first music library manager that fetches tags and re-files audio using configurable rules, plugins, and repeatable workflows.
Plugin system that extends matching and metadata sources while preserving the core library pipeline.
beets fits environments that need integration depth and predictable metadata updates across large music libraries. Its configuration system drives what to scan, how to match, and which write operations to perform, which reduces per-run variance in throughput and metadata output. A plugin architecture adds extensibility for custom matching, custom metadata sources, and additional processing steps.
A key tradeoff is that beets automation is driven primarily by configuration and Python plugins rather than a web UI, so governance requires disciplined rule management and testing. beets works well in workflows where library updates run as scheduled jobs and require auditability through consistent rule sets and reproducible runs. A common situation is an operations script that re-tags newly ingested audio files while preserving manual overrides.
- +Rule-driven tag writing with deterministic configuration
- +Plugin architecture for extensibility across metadata sources
- +Python API surface enables automation and custom tooling
- +Schema-like configuration supports repeatable library processing
- –Governance is configuration-centric with limited native RBAC
- –No built-in admin UI for approvals, reviews, or audit log views
- –Custom workflows often require Python plugin development
Media operations teams
Nightly ingestion and re-tagging of a growing music library
Lower manual QA time by ensuring consistent tag schema outputs per run.
Library automation engineers
Integration with internal ingestion pipelines and quality gates
More reliable decisions on when to overwrite tags versus preserve existing values.
Show 2 more scenarios
Independent label or curator teams
Maintaining a curated catalog with controlled metadata updates
Consistent catalog metadata that aligns with internal standards across releases.
beets configuration can target only specific libraries or file groups and apply metadata updates according to curated matching rules. Plugins can support curator-specific metadata extraction and normalization steps.
Systems integrators and automation studios
Building a custom tagging service that routes requests to beets workers
Higher throughput for batch tagging while keeping logic centralized in a maintainable rule set.
A beets-driven worker model can accept library update jobs and apply configured matching and writing pipelines. The extensibility model supports custom integrations for new metadata sources and transformation rules.
Best for: Fits when teams need configurable, repeatable tag automation with API-driven integration.
TagScanner
desktop taggerA Windows desktop tagger that batch-reads and writes common tag formats and supports metadata lookups and reformatting workflows.
Rules-based filename and tag formatting that updates multiple files in batch.
TagScanner supports batch tagging from local scans and tag sources, then writes changes across selected files with consistent field mapping. The data model centers on audio file properties plus common tag schemas, with tooling for renaming files, sorting by metadata, and applying edits in groups. The automation depth is practical for music libraries, with repeatable actions that can be re-run after collection changes.
A tradeoff appears in admin and governance controls, because TagScanner runs as a local desktop application rather than a multi-user service. Teams needing RBAC, centralized audit logs, or controlled provisioning typically need a separate operational layer around desktop usage. TagScanner fits a workflow where a curator maintains a workstation-based tagging pipeline for steady ingestion volumes and prefers visual verification before writing metadata.
- +Bulk tag editing across many files with field-level consistency
- +Rules for renaming and formatting files from tag values
- +Metadata sourcing and album art fetching for batch normalization
- +Repeatable desktop workflows for ongoing library updates
- –Limited admin governance since it is primarily local desktop usage
- –Few signs of an external API surface for programmatic provisioning
Independent music library maintainers
Normalizing tags and artwork after importing a large collection from mixed sources
A consistently tagged library with standardized filenames ready for media players and folders.
Local DJ and media organizers
Preparing a gig-ready track set with corrected titles, artists, and album fields
Reduced mislabeling during set prep and faster track selection in music software.
Show 2 more scenarios
Small home studios and cataloging workflows
Aligning project exports and mastered versions to a consistent tag schema
A stable metadata schema that simplifies session management and archival searches.
TagScanner can write tag updates across large file sets and keep tag formats consistent across versions. Rules for file naming support predictable storage structures for later retrieval.
Music archives with semi-regular curation
Ongoing enrichment of a curated archive after new batches are added
Lower manual cleanup time and more uniform records across repeated ingestion cycles.
TagScanner supports re-running bulk tagging workflows when new files arrive, then applying formatting rules for normalization. Desktop verification supports human review before metadata writes at scale.
Best for: Fits when music curators need fast desktop bulk tagging without server automation requirements.
Music Tag Studio
desktop tag editingA music tagging application that supports batch tag editing and structured metadata operations for common audio file formats.
Rule-based schema mapping for batch tag updates across music library sources.
Music Tag Studio targets music library cleanup through a structured tag data model and configurable import and sync workflows. Integration centers on schema-driven mapping between source metadata and tag fields, with an automation surface for batch operations.
The setup supports governance patterns such as controlled provisioning of tag rules and reproducible configurations across libraries. Administration and extensibility hinge on how far the automation and API surface can carry schema and workflow decisions end to end.
- +Schema-based tag mapping reduces field mismatch during large library imports
- +Batch automation supports repeatable tagging workflows across folders and libraries
- +Extensibility focuses on configuration-driven rules instead of manual edits
- +Governance patterns fit shared tagging standards through reusable workflow definitions
- –Integration depth depends on the available connectors for metadata sources
- –API and automation capabilities can be limited for custom tag pipelines
- –RBAC granularity may be constrained for multi-admin environments
- –Audit log coverage may not capture every field-level change in workflows
Best for: Fits when teams need consistent, schema-driven tagging automation with defined governance controls.
MP3Tag
batch editorA Windows batch tag editor that updates ID3 tags and other metadata through configurable field templates and multi-file workflows.
Filename pattern mapping generates tag values from naming conventions during batch imports.
MP3Tag batch-edits audio metadata such as ID3v1 and ID3v2 tags across large MP3 and compatible file sets. It provides a structured data model with tag fields, field mappings, and filename pattern rules for consistent naming and metadata generation.
Integration depth is mostly local to desktop workflows, since MP3Tag focuses on file-based operations rather than external API endpoints. Automation relies on repeatable actions like scripting, template-based tagging, and bulk processing with predictable throughput.
- +Batch processing applies consistent tag changes across large libraries
- +Field mapping and filename pattern rules reduce manual metadata entry
- +Scriptable tagging automates repeatable transformations
- +Supports common tag standards including ID3v2 and ID3v1
- –Desktop-first workflow limits direct integration with external systems
- –No documented provisioning path for centralized RBAC or policy enforcement
- –Audit log coverage is limited for governance-oriented environments
- –Extensibility via scripts depends on local execution context
Best for: Fits when local tagging workflows need repeatable automation without server-side integration.
Kid3
cross-platform editorA cross-platform tag editor that bulk updates ID3 and container tags with scripting-like batch operations.
Rule-based batch renaming and tag rewriting driven by configurable field expressions.
Kid3 suits personal libraries and small teams that need local music tag correction with repeatable mappings. It builds tag data around a schema of fields like artist, album, and track, then renders updates to files and folders.
Automation comes through scripts, import and export workflows, and rule-based transformations that apply consistently across batches. Integration depth is mostly local file operations rather than external-system APIs, so extensibility depends on formats, plugins, and scripted tooling.
- +Batch tag editing with rule-based transformations across folders
- +Clear tag data model aligned to standard music metadata fields
- +Scriptable automation for deterministic renaming and mapping
- +Import and export workflows for repeatable metadata cleanup
- –Limited external API surface for system-to-system integration
- –Governance controls like RBAC and audit logs are not a focus
- –Automation extensibility relies on local scripts and file formats
- –Throughput depends on local disk I/O rather than server pipelines
Best for: Fits when local batch tagging needs repeatable transformations without external integrations.
Mp3tagger
desktop metadataA tag management tool that edits metadata for audio files with batch processing and tag normalization features.
Batch rename and tag write rules driven by configurable mappings for consistent library-wide metadata.
Mp3tagger focuses on local metadata editing for audio files with fast batch tagging and consistent tag field handling. The tool centers on a practical data model built around embedded ID3 and Vorbis fields, plus flexible import and write rules for large libraries.
Automation is driven by batch workflows and configurable mappings for file renaming and tag population, rather than external orchestration. Integration depth is limited to desktop workflows, with no documented API or extensibility surface for admin automation and RBAC governance.
- +Batch tagging across folders with predictable tag field updates
- +Flexible filename-to-tag and tag-to-filename renaming workflows
- +Support for common ID3 and Vorbis tag fields in one editor
- +Import and write rules reduce manual corrections across large libraries
- –No documented API or automation surface for external systems
- –Limited governance controls like RBAC and audit logs
- –Local desktop workflow limits integration with admin provisioning
- –Automation throughput depends on single-machine batch processing
Best for: Fits when local music libraries need repeatable batch tagging without external integrations.
Tag & Rename
batch editorA Windows batch tag editor and renamer that maps audio metadata fields into configurable naming schemes.
Tag-to-filename pattern rules for bulk renaming driven by selected metadata fields.
Tag & Rename focuses on local music file management with tag edits and automated renaming rules applied directly to files. It supports batch operations, metadata-based transformations, and configurable naming patterns that map tags into filenames.
Integration depth is mostly limited to file-system workflows rather than external systems or remote catalog sync. The automation surface is rule-driven for repeatable throughput, with extensibility centered on how schemas and placeholders are defined for transformations.
- +Rule-based batch renaming that maps tag fields into filename patterns
- +Configurable transformation patterns support repeatable library cleanup
- +Local file edits reduce dependency on external music catalogs
- +Metadata-driven workflows fit high-throughput tagging passes
- –Limited external integration depth versus API-first tag management
- –Automation governance like RBAC and provisioning is not a built-in concept
- –No documented API surface for programmatic tag processing pipelines
- –Audit log and change history controls are not suited for enterprise governance
Best for: Fits when local libraries need repeatable batch tag and rename automation without external integration.
How to Choose the Right Music Tag Software
This buyer's guide covers music tag software tools that write tags and rename files using rules, batch workflows, and metadata lookups. It includes MusicBrainz Picard, beets, TagScanner, Music Tag Studio, MP3Tag, Kid3, Mp3tagger, and Tag & Rename.
The guide focuses on integration depth, data model choices, automation and API surface, and admin and governance controls. Each section maps concrete tool behaviors to selection criteria so the right tagging workflow can be implemented without trial-and-error.
Music tag tools that normalize metadata at scale using rules, schemas, and library workflows
Music tag software updates ID3 and other embedded metadata fields and can also rename files based on tag values and filename patterns. It solves library cleanup problems like inconsistent artist or track mapping and repeated manual correction across large local collections.
MusicBrainz Picard assigns metadata by matching audio to MusicBrainz entities and applying configurable tagging rules. beets applies deterministic, repeatable tag pipelines with a Python API surface and a plugin architecture that fetches tags and refiles audio using configuration-driven workflows.
Evaluation criteria for tagging automation, schema discipline, and controlled change
Tagging tools fail in specific ways when the data model is weak, the rules are not repeatable, or automation cannot integrate with other systems. The strongest options also expose configuration or code surfaces that support repeatable throughput across folders or libraries.
Governance matters when multiple admins touch the pipeline, since many desktop-first tag editors keep changes local and do not provide RBAC, provisioning, or audit views. Integration depth also determines whether tagging stays a local batch job or becomes an automation component in a broader workflow.
Integration depth tied to metadata entities and import or export formats
MusicBrainz Picard excels when MusicBrainz entity alignment is required because its workflow maps MusicBrainz releases to recording and track fields using its configurable rule system. Tools like TagScanner, MP3Tag, and Kid3 remain mostly file-system and desktop-oriented, which limits system-to-system orchestration.
Rule engine that turns metadata into filenames and tag field values
For predictable renaming and consistent tag writing, tools like MusicBrainz Picard, TagScanner, and MP3Tag provide rules that translate values into filenames and embedded fields. Kid3 and Mp3tagger also use configurable field expressions or mappings that drive deterministic batch updates.
Structured data model for tag fields and schema-like mapping
Music Tag Studio uses schema-based tag mapping to reduce field mismatch during batch library imports and sync workflows. beets uses a clear configuration and data model for tags, sources, and pipeline behavior so the same library processing logic can be reused across runs.
Automation and API surface for programmatic orchestration
beets stands out because it includes a documented Python API surface plus plugins that extend matching and metadata sources while preserving the core library pipeline. MusicBrainz Picard supports a plugin ecosystem, but its centralized RBAC, provisioning, and audit controls remain limited and its automation surface is less suited to server-side orchestration.
Extensibility via plugins or scripts with controlled transformations
beets offers a plugin architecture for new sources and matching logic, which enables extending metadata fetching and tag updates without rewriting the whole pipeline. MP3Tag scripting and Kid3 script-like batch operations provide local extensibility for deterministic transformations when server integration is not required.
Admin and governance controls for safe multi-admin tagging
Music Tag Studio supports governance patterns through reusable workflow definitions and schema-driven mapping that can standardize how tag rules are provisioned. MusicBrainz Picard, beets, and MP3Tag have limited native RBAC, provisioning, and audit log coverage, which makes workstation-level discipline a key requirement for controlled change.
Choose based on where tagging logic runs and how changes are controlled
The first decision is where the tagging pipeline must run. MusicBrainz Picard, TagScanner, MP3Tag, Kid3, Mp3tagger, and Tag & Rename center on local batch workflows, while beets adds a documented Python API surface that supports external automation.
The second decision is whether tagging rules need to be standardized across a team. Music Tag Studio and MusicBrainz Picard emphasize rule configuration and schema-driven mapping, but governance depth differs because centralized RBAC, provisioning, and audit log controls are limited in multiple desktop-first tools.
Pick a primary matching and entity source model
If MusicBrainz entity mapping is the core source of truth, choose MusicBrainz Picard because it matches releases and maps recordings and tracks using configurable tagging rules. If a custom or script-driven matching workflow is needed, pick beets because it fetches tags through a plugin-based pipeline built around deterministic configuration.
Define the data model target before evaluating file renaming
When tag field mapping must be consistent across imports, use Music Tag Studio because schema-based tag mapping reduces field mismatch during batch operations. When the focus is tag field updates driven by naming conventions, MP3Tag and Kid3 use filename pattern rules and field expressions to generate consistent tag values.
Require an API or automation surface only when it will be used
If orchestration is needed in other systems, select beets since it provides a documented Python API surface and a plugin architecture that keeps the pipeline behavior consistent. If the workflow can stay a local batch job, TagScanner, MP3Tag, Mp3tagger, and Kid3 can meet throughput needs without external endpoints.
Validate governance needs against the tool’s real admin controls
For repeatable tagging standards across shared libraries, use Music Tag Studio because schema-driven mapping and reusable workflow definitions support shared tagging standards. For tools like MusicBrainz Picard, beets, and MP3Tag, plan governance around workstation configuration discipline since centralized RBAC, provisioning, and audit log views are limited.
Stress-test repeatability using batch rules and dry-run style workflows
For high-throughput local libraries, MusicBrainz Picard supports local batch processing with confirmation steps and rule-based tag writing, which reduces inconsistent batch edits. For other desktop batch editors like TagScanner and MP3Tag, verify that the filename pattern rules and field mappings apply consistently across folders in a single run.
Tool fit by operating model, from local desktop batch edits to API-driven automation
Different teams want different execution models for tag normalization. Some need a local curator workflow that can rename and write embedded tags quickly, while others need programmable pipelines that can be integrated into broader automation.
The best fit also depends on whether centralized governance like RBAC and audit visibility is required. Several tools keep governance local and focus on deterministic tagging rules and batch throughput.
Teams standardizing library tagging against MusicBrainz
MusicBrainz Picard fits teams that need controlled local batch tagging aligned to MusicBrainz metadata because it applies MusicBrainz release lookups and maps recordings and tracks through configurable tagging rules.
Engineering teams building automation around tag pipelines
beets fits teams that need API-driven integration because it provides a documented Python API surface and a plugin system that extends matching and metadata sources while preserving the core library pipeline.
Desktop curators running high-throughput local bulk edits
TagScanner fits curators who need fast Windows desktop bulk tagging without server automation because it supports rules-based filename and tag formatting across large file batches with album art handling. MP3Tag also fits this local throughput model using template-based field mapping for ID3v2 and ID3v1.
Teams that require schema-driven mapping and reusable workflow governance
Music Tag Studio fits teams that need consistent, schema-driven tagging automation with defined governance controls because it uses schema-based tag mapping and configurable import and sync workflows.
Local-first libraries using rule-based renaming and deterministic tag rewrites
Kid3, Mp3tagger, and Tag & Rename fit local libraries that need repeatable batch renaming and tag rewriting without external integrations because they use configurable field expressions, mappings, and tag-to-filename pattern rules.
Pitfalls that cause inconsistent metadata and weak control over tag changes
Many tagging failures come from picking a tool that cannot express the transformation rules needed for renaming and field updates. Other failures come from governance gaps like missing centralized RBAC, provisioning, and audit log coverage.
These pitfalls show up repeatedly across desktop-first tag editors and also affect automation-first tools when multi-admin control is required.
Selecting a desktop-first editor without an automation or API surface
Avoid using MP3Tag, TagScanner, Kid3, Mp3tagger, or Tag & Rename as the center of a server-driven pipeline because each tool is primarily local file-based batch editing with no documented API surface for external orchestration. Use beets when automation must integrate into other systems via its documented Python API surface.
Assuming governance exists without centralized RBAC and audit views
Avoid planning multi-admin approvals or traceable governance around MusicBrainz Picard, beets, and MP3Tag because centralized RBAC, provisioning, and audit log controls are limited. Choose Music Tag Studio when schema-driven reusable workflow definitions are needed to standardize tagging rules across admins.
Using ad hoc field renaming rules that do not map consistently across runs
Avoid creating one-off filename pattern rules in tools like MP3Tag or Tag & Rename without verifying field mappings across a full batch. Prefer deterministic rule pipelines in MusicBrainz Picard, TagScanner, or beets so tag-to-filename and filename-to-tag behavior stays repeatable.
Skipping schema mapping during library imports with inconsistent metadata sources
Avoid using only field-level edits when imports mix inconsistent tag formats because schema mismatch can propagate through batch updates. Use Music Tag Studio for schema-based tag mapping and use MusicBrainz Picard when MusicBrainz release lookups are available to drive consistent track and recording mapping.
How We Selected and Ranked These Tools
We evaluated each music tag software tool on features for batch tag writing and rule configuration, ease of use for practical library workflows, and value tied to repeatability and integration potential. Features carries the most weight at forty percent, while ease of use and value each account for thirty percent in the overall score. This ranking is based on editorial research from the provided tool capabilities and workflow descriptions rather than private benchmark tests.
MusicBrainz Picard set the pace because configurable tagging rules translate MusicBrainz entities into written filename and tag fields, which ties strong features directly to the use case of controlled local batch tagging aligned to MusicBrainz metadata.
Frequently Asked Questions About Music Tag Software
Which music tag tools offer a deterministic rules engine for repeatable batch tagging?
How do MusicBrainz Picard and beets differ when mapping audio metadata to releases?
Which tool is best for high-throughput local bulk tagging with confirmation steps?
What options exist for integrating tag automation with other systems via API or scripting?
Do these music tag tools support SSO, RBAC, and audit logs for team governance?
How should a team migrate from one tag schema and filename convention to another?
Which tools provide stronger admin controls through governed configuration provisioning?
What common failure modes occur during bulk tag normalization and how do the tools mitigate them?
Which tool handles album art and multi-field batch updates more directly in a desktop workflow?
Conclusion
After evaluating 8 music and audio, MusicBrainz Picard 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
Music And Audio alternatives
See side-by-side comparisons of music and audio tools and pick the right one for your stack.
Compare music and audio 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.