GITNUXSOFTWARE ADVICE
General KnowledgeTop 10 Best Plant Collection Software of 2026
Ranked list of the top plant collection software for herbarium databases and plant records, with comparisons and tradeoffs for researchers, including IrisBG.
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
IrisBG is the best fit for botanical gardens and arboreta that need tight curation history, consistent locality records, and clear labeling outputs, whereas CollectionSpace works best when a herbarium wants a more structured, open-source specimen workflow with external publishing integration.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
IrisBG
Determination history is stored as part of the record lifecycle so accepted-name changes remain auditable per specimen.
Built for fits when herbarium or living-collection teams need curation history, labeling outputs, and locality consistency..
Hortis
Editor pickCuration workflows that keep determinations and related edits connected to recorded changes over time.
Built for fits when botanical teams need repeatable curation workflows and export-ready records for ongoing additions..
CollectionSpace
Editor pickAuthority-first taxonomic handling with determination history support for consistent naming across large specimen backlogs.
Built for fits when herbaria need structured specimen workflows, authority control, and external publishing integration..
Comparison Table
IrisBG
vertical specialistCollection management software for botanical gardens, arboreta, and living plant collections.
Determination history is stored as part of the record lifecycle so accepted-name changes remain auditable per specimen.
IrisBG is positioned for teams that need more than simple catalogs because it carries curation context through the lifecycle of a record. Record fields connect collector and collecting event details, locality attributes, and identification changes so determination history stays tied to the specimen or living plant record. IrisBG’s data entry surfaces are oriented around ongoing accession management and routine herbarium backlogs.
A tradeoff appears in implementation depth because IrisBG’s strongest results depend on consistent taxonomy setup and internal naming conventions before large batch imports. The best usage situation is a small-to-mid herbarium database or living collections database that will keep evolving identification and locality data rather than only ingesting legacy records once.
- +Determination history keeps ID changes tied to each specimen record
- +Locality capture fields reduce inconsistent geodata entry patterns
- +Accession-centered workflows fit ongoing curation and backlog processing
- +Synonym-aware taxonomy handling supports accepted-name continuity
- –Strong taxonomy setup effort is required before large-scale imports
- –Advanced integration needs require custom work for non-native workflows
Herbarium curators
Track determinations over time
Fewer mismatched ID histories
Collection managers
Run accession workflows
Lower backlogged accession work
Show 2 more scenarios
Field botanists
Record locality and collecting events
More consistent locality data
Collectors enter locality details alongside collector and event metadata for later curation.
Taxonomy coordinators
Maintain accepted-name continuity
Less synonym duplication
Coordinators manage synonym pathways so determinations resolve to a stable accepted name.
Best for: Fits when herbarium or living-collection teams need curation history, labeling outputs, and locality consistency.
Hortis
vertical specialistBotanical collection management software for gardens, arboreta, and plant institutions.
Curation workflows that keep determinations and related edits connected to recorded changes over time.
Hortis fits herbarium databases and botany teams that need consistent records across accessions and ongoing edits. Record pages support typical collection data entry, while curation workflows keep determinations and metadata updates tied to specific changes. For teams integrating multiple projects, search and filtering across common metadata fields helps staff locate duplicates and reconcile edits.
A key tradeoff is that deep interoperability depends on the level of export and external integration configured for a given deployment. Hortis works best when the team commits to a shared labeling and data-entry standard before migrating historical vouchers and collector notes.
Teams doing frequent re-determinations and adding locality refinements benefit from repeated use of the same structured entry patterns. Publishing for downstream audiences is most useful when the dataset is already cleaned into a consistent taxonomic authority approach.
- +Curation workflow ties metadata edits to structured determination updates
- +Batch import supports faster migration from spreadsheets into records
- +Record organization and filtering help track inconsistencies across updates
- +Publishing outputs support sharing curated plant records with external consumers
- –Advanced interoperability needs careful setup of exports and external workflows
- –Taxonomic reconciliation requires governance to avoid authority drift
- –Complex labeling and field mapping can require iterative import tuning
- –Workflow configuration depth can slow adoption for very small teams
Herbarium database teams
Track re-determinations across vouchers
Fewer conflicting versions in records
Living collections managers
Maintain accession-like living records
Cleaner operational records over time
Show 2 more scenarios
Data migration leads
Import historical spreadsheets into Hortis
Faster onboarding with fewer edits
Migrators map fields during batch import to reduce manual re-entry of past records.
Research data publishers
Publish curated plant records externally
Consistent published record sets
Publishers generate outputs from curated records to share with downstream biodiversity audiences.
Best for: Fits when botanical teams need repeatable curation workflows and export-ready records for ongoing additions.
CollectionSpace
enterpriseOpen-source collections management software for museums, archives, and research collections.
Authority-first taxonomic handling with determination history support for consistent naming across large specimen backlogs.
CollectionSpace supports accession-style specimen lifecycles with structured provenance fields, which helps teams keep collector and event context tied to each voucher specimen. The software’s model is designed to support determination history workflows, including accepted name tracking and synonym mapping against taxonomic authority data. For organizations moving between spreadsheets and a shared herbarium record repository, CollectionSpace includes import tooling and export outputs used in biodiversity data publishing workflows.
A key tradeoff is that deeper configuration is often required to match a herbarium’s local schema and labeling conventions, which can slow initial rollout. CollectionSpace works best when a team needs multi-person data entry with consistent field constraints and when specimen records must integrate with external taxonomic services or downstream publishing formats. A common usage situation is building a consolidated living collections database or herbarium management system that multiple curators update while an integration layer publishes updates to external aggregators.
- +Schema configuration supports herbarium-specific specimen and determination workflows
- +Authority-driven name handling keeps accepted names aligned across records
- +Bulk import and export support repeatable data migration cycles
- +API and integration hooks fit multi-system collection data pipelines
- –Initial configuration takes time to match local herbarium schema
- –Some workflows need curator training to avoid data-model inconsistencies
- –Labeling and mapping workflows can require extra setup effort
- –Extensibility often depends on local integration engineering
Herbarium data managers
Consolidate curator edits into one record
Cleaner, consistent herbarium records
Biodiversity data publishing teams
Export updated records on schedule
Fewer manual export errors
Show 2 more scenarios
Museum integration engineers
Sync CollectionSpace with external systems
Automated cross-system updates
Connects specimen records to other services via API-driven and batch-based integration points.
Collection-wide governance leads
Standardize taxonomy and event fields
Uniform authority and provenance
Centralizes controlled vocabularies and authority references for shared provenance data.
Best for: Fits when herbaria need structured specimen workflows, authority control, and external publishing integration.
Catalogue of Life
API-firstChecklist and taxonomy reference used for plant species data alignment in collection databases.
API-driven taxon concept and synonym integration for turning raw names into accepted-name references.
Catalogue of Life is a taxonomic reference database focused on standardizing botanical nomenclature and accepted names across the tree of life. Its core value for plant collection workflows comes from integrating authority-backed taxonomy into downstream herbarium records and biodiversity reporting.
The site centers on taxon concepts, synonym relationships, and nomenclatural status fields that can be reused when mapping collection data to published standards. For automation, Catalogue of Life provides an API surface that supports programmatic lookups of taxon identifiers and names.
- +API supports programmatic taxon lookups by identifiers and names
- +Accepted name and synonym relationships reduce manual nomenclature work
- +Published taxon concepts help keep herbarium records consistent at scale
- +Stable taxonomic identifiers support long-running data integration jobs
- –Not a dedicated herbarium specimen module for specimen-level management
- –Taxonomy-first scope leaves accession workflows outside its core features
- –Complex taxon matching can require curation outside the API calls
- –Governance and RBAC controls for internal staff are not the focus
Best for: Fits when herbarium systems need authoritative plant taxonomy IDs for records and publishing pipelines.
BG-BASE
vertical specialistBotanical garden database software for managing living plant collections and associated records.
Accession-centric record history that keeps determination evolution linked to provenance and locality fields.
BG-BASE supports plant collection workflows centered on accession records, specimen-like entities, and collection provenance. It includes horticulture- and herbarium-adjacent fields that map collector data, determinations, and locality details into a single record space.
The system focuses on ongoing data maintenance and history tracking rather than only data entry. Administration emphasizes structured configuration for controlled vocabularies and record lifecycles.
- +Accession-first workflow ties determinations and provenance to one record spine
- +Structured history supports determination changes without losing earlier context
- +Controlled field configuration helps keep locality and naming entries consistent
- +Label-ready record fields support routine cataloging and inventory updates
- –API documentation and integration depth need validation for external herbarium pipelines
- –Complex taxonomic workflows can feel heavy without careful template design
- –Automation options appear more configuration-driven than code-driven
- –Bulk migration of legacy records may require preprocessing to match field constraints
Best for: Fits when herbarium and living-collection data share the same accession-driven workflows.
Planta
SMBPlant care app that organizes household plants and tracks care schedules.
Profile-first collection building with collaborative sharing designed for ongoing living-collection updates.
Planta is plant collection software built around personal-to-institution workflows that track plants as living records and link them to field and care history. Its core setup focuses on collection organization, plant profiles, and observational notes that can support herbarium-adjacent use like voucher context and cultivation-based provenance trails.
The software adds sharing and collaboration through controlled access to collection data, which helps teams align determinations and record updates. Planta also supports extensibility through imports and integrations so teams can move data in without rewriting every workflow.
- +Human-readable plant profiles reduce friction during daily data entry
- +Sharing and collaboration support keeps multi-person records synchronized
- +Import workflows help move existing collections without recreating data manually
- +Customizable fields and tags fit mixed collection practices
- –Herbarium-scale accession number workflows need careful structuring
- –Schema-oriented publishing for biodiversity data mapping is limited
- –Advanced determination history tracking requires process discipline
- –Exchange and loan workflows are not built for collection logistics
Best for: Fits when small to mid-size teams need fast living-collection recordkeeping with light herbarium linkage.
Plant Parent
SMBPlant identification and care app for organizing plants and managing care reminders.
Curation-oriented record history that keeps updates tied to the plant record during day-to-day maintenance.
Plant Parent positions itself as plant collection software focused on keeping plant records actionable for collection work, not only data entry. It centers on collection management workflows like maintaining specimens and connecting records to taxonomic names.
The system supports organizing records for ongoing curation through status and history-style fields that track what changed and when. Integration depth depends on Plant Parent’s available import, export, and API support for external systems used by herbaria and research groups.
- +Collection record workflow is oriented around ongoing curation
- +Taxonomic name handling reduces friction when names change over time
- +Label-ready record fields support consistent documentation
- +History-style tracking helps reviewers see what was updated
- –Automation surface is less clear for large batch imports and fixes
- –External system integration options appear limited without developer support
- –Governance controls are not as detailed as in enterprise herbarium stacks
- –Advanced exchange and loan workflows need custom handling
Best for: Fits when small herbarium teams need structured plant records with manageable curation workflows.
Specify Collections
enterpriseCollections management software for natural history institutions and biodiversity research.
Determination history management ties updated identifications to dates and responsible parties.
Specify Collections is a collections data system for herbarium-style workflows that focuses on capturing specimens, observations, and event history in one place. The product emphasizes specimen-centric record structures, taxon handling, and management of determinations across time.
It supports collection-wide administration features for roles and structured data capture, with an integration surface that fits institutions building around existing data pipelines. Specify Collections also fits teams that need consistent labeling outputs and repeatable data entry processes for voucher and locality-linked records.
- +Specimen-centric workflows support determinations across time without duplicating records
- +Taxon handling supports accepted name and synonym relationships for record linking
- +Label output workflows support consistent accession-style documentation
- +Structured event capture helps keep collector and locality provenance tied to records
- –Herbarium-specific setup requires disciplined configuration of fields and rules
- –Complex automation beyond standard workflows depends on integrating external systems
- –Cross-collection reporting can require careful data modeling to avoid inconsistent outputs
- –Customization depth can increase admin overhead for maintaining schemas and mappings
Best for: Fits when herbarium teams need controlled specimen records with determination history and consistent label workflows.
Arctos
enterpriseCloud collections management system for natural history specimens and biodiversity data.
Determination history stores successive taxonomic decisions with contextual provenance tied to the record lifecycle.
Arctos (arctosdb.org) manages herbarium and related specimen records with a workflow that links collections data to taxonomic and authority-controlled concepts. Its core capabilities center on accession and cataloging processes, determination and provenance tracking, and collection-wide reporting for curator review.
Arctos also supports data sharing via structured exports and a documented integration surface that lets other systems exchange specimen and locality information. Administration focuses on governed user access and audit-friendly operational controls across collection-related actions.
- +Authority-driven taxonomy linking reduces synonym drift across specimen records
- +Accession-to-catalog workflows fit curator-managed herbarium operations
- +Provenance and determination history are first-class fields, not add-ons
- +Structured exports support biodiversity data publishing pipelines
- –Herbarium-specific workflows require training to avoid record fragmentation
- –Some advanced automation needs technical help to implement at scale
Best for: Fits when herbarium teams need curator-grade governance and history tracking across accessioned specimens.
EMu
enterpriseElectronic Museum management system for natural history collections including botanical specimens.
Specimen-centric workflow depth with accession numbering and label generation tied to record governance controls.
EMu by Axiell (axiell.com) is a herbarium and collections information system built around cataloging, specimen-linked record maintenance, and long-term curatorial workflows. It supports accession management workflows such as numbering, labeling, and structured record linking for voucher specimens.
The system’s integration options include extensibility through APIs and data exchange patterns used to connect herbarium holdings to external biodiversity data publishing pipelines. Governance is handled through configuration of roles and permissions and through audit-oriented operational controls used in multi-curator environments.
- +Strong accession and specimen record linking for curatorial workflows
- +Extensibility supports custom integrations via API and data exchange
- +Label-ready record structures help maintain consistent IDs across systems
- +Configuration supports multi-role operations for collection staff and data stewards
- –Advanced configuration can slow down onboarding for new data managers
- –Schema changes can be operationally heavy when record structures evolve
- –Complex taxonomic workflows require disciplined authority management setup
- –High-volume imports need careful throughput planning to avoid delays
Best for: Fits when herbaria need accession-driven voucher management and integration to publishing targets.
Conclusion
After evaluating 10 general knowledge, IrisBG 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.
How to Choose the Right plant collection software
Plant collection software manages herbarium records, living-collection updates, and voucher-specimen lifecycles from accession to determination history. This buyer's guide covers IrisBG, Hortis, CollectionSpace, Catalogue of Life, BG-BASE, Planta, Plant Parent, Specify Collections, Arctos, and EMu.
The tool set is weighed for integration depth, automation and API surface, and admin and governance controls that hold up under curator workflows and taxonomic change. The sections that follow focus on how each system handles accepted-name changes, determination edits, and authority alignment at the specimen or record level.
Plant collection software for accession management, determination history, and curated herbarium workflows
Plant collection software is a record system for specimen-level work that links collector and collecting event metadata, locality capture, and accession number governance to identification changes over time. IrisBG stores determination history as part of each specimen record lifecycle so accepted-name changes remain auditable per specimen, while Hortis ties metadata edits to structured determination updates.
Many teams also need authority handling for botanical nomenclature so accepted names and synonyms stay consistent across backlogs. CollectionSpace prioritizes authority-first taxonomic handling with determination history support across structured specimen workflows, while Catalogue of Life emphasizes API-driven taxon lookups and synonym integration for accepted-name references.
Plant collection software features that affect curator workflows and taxonomic change control
A plant collection system must keep determination changes traceable to each specimen or accession record, because accepted-name edits happen repeatedly during curation. These features decide whether curation stays auditable and export-ready when taxonomy updates ripple through backlogs.
Determination history bound to the record lifecycle
IrisBG stores determination history as part of each specimen record lifecycle, so accepted-name changes remain auditable per specimen. Hortis keeps curation workflows tied to structured determination updates so metadata edits and determinations stay connected over time.
Authority-first taxonomic handling for accepted names
CollectionSpace uses authority-first taxonomic handling with determination history support for consistent naming across large specimen backlogs. Catalogue of Life emphasizes API-driven taxon lookups and synonym integration to map raw names to accepted-name references.
Schema configuration for herbarium-specific specimen workflows
CollectionSpace includes schema configuration for herbarium-specific specimen and determination workflows. Specify Collections requires disciplined configuration of fields and rules to keep herbarium-specific setup from producing data-model inconsistencies.
Accession-centric record history across provenance and locality
BG-BASE uses an accession-first workflow that ties determinations and provenance to one record spine. Arctos also fits curator-managed herbarium operations with accession-to-catalog workflows and context tied to the record lifecycle.
Extensibility through API and data exchange for non-native pipelines
EMu supports extensibility for custom integrations via API and data exchange while retaining accession-number and label-generation governance controls. Catalogue of Life offers an API-driven taxon concept for programmatic taxon lookups by identifiers and names.
Batch import and export behavior for record migration
Hortis includes batch import that supports faster migration from spreadsheets into records while preserving determination and metadata edit links. IrisBG fits large-scale imports only after strong taxonomy setup because strong taxonomy setup effort is required before importing at volume.
How to choose plant collection software by workflow depth, governance, and integration shape
Plant collection platforms differ most by where they anchor record truth, either to a specimen record spine or to an accession-centric model. The second biggest split is how much governance discipline is needed to keep authority handling and determination histories consistent at scale.
Pick the record spine that matches how curation staff edits data
If the team expects auditable ID changes per specimen, IrisBG keeps accepted-name changes tied to each specimen record lifecycle. If curation work is managed as ongoing metadata updates linked to structured determination updates, Hortis connects metadata edits to determinations over time.
Decide whether authority control is built into the specimen workflow or provided as an external taxonomy service
If authority control must happen inside specimen workflows, CollectionSpace uses authority-first taxonomic handling with determination history support. If authority mapping will be driven through programmatic taxon lookups, Catalogue of Life provides API support for identifiers and names plus accepted-name and synonym relationships.
Choose the deployment workflow that fits the team’s schema ownership
If the herbarium can invest time in matching local schema expectations, CollectionSpace supports schema configuration for herbarium-specific specimen and determination workflows. If the team prefers controlled specimen-centric workflows without extensive schema rework, Specify Collections supports specimen-centric workflows that rely on disciplined field and rule configuration.
Stress-test accession-first provenance and label governance against existing local practices
If the working model is accession-driven provenance and determination evolution, BG-BASE ties determinations and provenance to an accession record spine. If curator-grade governance and governance-linked accession-to-catalog workflows matter, Arctos anchors workflows to accession-to-catalog operations and records successive taxonomic decisions with contextual provenance.
Validate integration throughput and automation surface for external systems and batch fixes
If the pipeline needs custom integrations beyond native herbarium workflows, EMu supports extensibility via API and data exchange while retaining label generation tied to record governance controls. If the goal is to speed up migration while keeping curation connections intact, Hortis adds batch import from spreadsheets but needs careful export and external workflow setup for interoperability.
Plan for the taxonomy setup and governance burden before importing large backlogs
If accepted-name and determination history depend on strong taxonomy setup effort, IrisBG requires that work before large-scale imports. If authority drift risk exists, Hortis notes that taxonomic reconciliation requires governance to avoid authority drift.
Who plant collection software is built for based on curation scale and governance needs
Different plant collection systems align to different operational models for herbarium records, living-collection updates, and voucher specimen workflows. Teams should match software capabilities to the amount of taxonomic change and the level of curator governance required for acceptance-name consistency.
Herbarium teams that need auditable accepted-name changes per specimen record
IrisBG stores determination history inside each specimen record lifecycle so accepted-name changes stay auditable per specimen. CollectionSpace also supports authority-first taxonomic handling with determination history support for large specimen backlogs.
Botanical and curation teams that run repeatable workflows for ongoing additions
Hortis ties metadata edits to structured determination updates so curation stays connected to record changes over time. Hortis also supports batch import from spreadsheets to accelerate migration into records.
Institutions that need taxon mapping via API and synonym relationships for publishing pipelines
Catalogue of Life offers an API-driven taxon concept with synonym integration to turn raw names into accepted-name references. It fits publishing pipelines that require programmatic taxon lookups by identifiers and names.
Small to mid-size teams managing living collections with collaborative updates
Planta builds collections through human-readable plant profiles and collaborative sharing for multi-person synchronization. Planta is positioned for daily living-collection recordkeeping rather than full herbarium-scale accession-number workflows.
Curator-managed herbarium operations that run accession-to-catalog processes
Arctos fits curator-managed herbarium operations with accession-to-catalog workflows and authority-driven taxonomy linking. BG-BASE also fits accession-driven workflows by tying determinations and provenance to one accession record spine.
Common mistakes when selecting plant collection software for herbarium records and determination history
Plant collection platforms fail most often when teams choose based on interface familiarity while ignoring how the system binds accepted-name changes to record history. Many failures also come from underestimating schema ownership, import preparation, and governance discipline for authority handling.
Choosing a taxonomy service for identifiers but expecting it to manage specimen-level voucher workflows
Catalogue of Life focuses on API-driven taxon concepts and accepted-name and synonym relationships, so it lacks a dedicated specimen module for accession workflows. EMu and IrisBG keep accession and specimen record governance inside curator workflows so voucher management stays tied to record lifecycles.
Importing large backlogs before taxonomy setup and reconciliation governance are ready
IrisBG requires strong taxonomy setup effort before large-scale imports to keep determination history consistent. Hortis also flags that taxonomic reconciliation requires governance to avoid authority drift.
Under-scoping schema configuration time and training requirements for herbarium-specific field rules
CollectionSpace can require time to match local herbarium schema and can need curator training to avoid data-model inconsistencies. Specify Collections similarly requires disciplined configuration of fields and rules to support controlled specimen records and determination history.
Assuming automation and integration depth are uniform across record types and batch operations
Arctos notes advanced automation may need technical help to implement at scale, which can slow large batch fixes. Hortis supports batch import but highlights that advanced interoperability needs careful setup of exports and external workflows.
How We Selected and Ranked These Tools
We evaluated determination-history behavior tied to each specimen or accession record lifecycle across IrisBG, Hortis, CollectionSpace, BG-BASE, Specify Collections, and Arctos. We evaluated authority handling pathways using CollectionSpace authority-first taxonomic handling and Catalogue of Life API-driven taxon lookups with accepted-name and synonym relationships.
We evaluated integration breadth and API surface using EMu extensibility via API and data exchange plus Catalogue of Life programmatic taxon lookup support. We weighted features at 40% and ease and value at 30% each, with IrisBG standing out because determination history remains auditable per specimen when accepted-name changes occur during the record lifecycle.
Frequently Asked Questions About plant collection software
How do IrisBG and Arctos store determination history when accepted names change?
Which herbarium systems expose an API for taxon or specimen integration rather than only exports?
How does CollectionSpace handle authority control for botanical nomenclature during curation?
What data migration path works best for teams moving from spreadsheets into herbarium collection systems?
What breaks if a team needs fine-grained admin controls and audit visibility across multiple curators?
When should herbaria pick an accession-centric workflow like BG-BASE instead of plant-profile workflows like Planta?
How do Hortis and Specify Collections differ in how they keep determinations tied to ongoing edits over time?
What tradeoff appears when a system emphasizes authority and taxonomy reference concepts versus specimen workflow depth?
How does EMu support voucher specimen labeling tied to accession numbering and governance controls?
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
General Knowledge alternatives
See side-by-side comparisons of general knowledge tools and pick the right one for your stack.
Compare general knowledge tools→