
GITNUXSOFTWARE REVIEW
Chemicals & Industrial MaterialsTop 10 Best Sieve Analysis Software of 2026
Compare sieve analysis software tools for lab use, covering features and tradeoffs for selecting systems that fit testing workflows.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy
Particle Technology Labs PTL-LIMS is the best pick for labs running frequent sieve stacks because its calibration-aware stack provisioning ties each gradation report to the aperture provenance and keeps batch traceability clean, while Microtrac MRB suits enterprise teams that need operator-agnostic, guided stack calculations that automatically generate cumulative passing curves.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Particle Technology Labs PTL-LIMS
Calibration-aware sieve stack provisioning ensures every gradation report carries the aperture provenance used for that batch.
Best for: Fits when labs run frequent sieve stacks and need traceable, standardized gradation reports.
Mecmesin Emperor
Editor pickInstrument-linked run processing that converts sieve stack measurements into standardized gradation report packages with consistent calculations.
Best for: Fits when labs run repeated sieving tests and need standardized gradation report outputs.
Microtrac MRB
Editor pickSieve stack driven calculations automatically generate cumulative passing curves and percent retained summaries tied to a single run.
Best for: Fits when labs need consistent sieve-based gradation reports across repeated operators and stack configurations.
Comparison Table
Particle Technology Labs PTL-LIMS
vertical specialistPTL-LIMS manages particle characterization laboratory data, sample tracking, and analytical reporting.
Calibration-aware sieve stack provisioning ensures every gradation report carries the aperture provenance used for that batch.
PTL-LIMS is built for geotechnical lab management where sieve stacks, sample mass, and run metadata drive repeatable gradation report generation. It handles routine dry sieving reporting and provides a cumulative passing curve view used in aggregate gradation checks. Particle count inputs can be organized by percent retained and pan fraction handling to support consistent mass balance verification across batches.
A key tradeoff is that PTL-LIMS emphasizes lab workflow control and report generation more than ad hoc numerical scripting, so custom calculations often require configuration through the application instead of direct MATLAB or Python edits. It fits when engineering teams need consistent gradation outputs across many test runs and want traceable calibration context per sieve and per batch.
- +Calibration-linked sieve stack configuration ties results to aperture provenance
- +Batch traceability connects sample mass and run metadata to each report output
- +Automated report generation reduces manual formatting errors across gradation deliverables
- +Supports consistent handling of pan fraction and percent retained summaries
- –Workflow-first design can slow highly custom calculation needs
- –Integration depth depends on available connectors for external systems
- –Sieve stack setup work is required before high-throughput batches
- –Export formatting for niche vendor templates may need manual mapping
Geotechnical lab analysts
Generate compliant gradation reports at scale
Faster review and fewer rework cycles
Quality managers
Trace sieve calibration to outcomes
Clear accountability per batch
Show 2 more scenarios
Engineering data leads
Standardize results across multiple teams
Consistent aggregate gradation reporting
Shared configuration for stacks and mass handling reduces variation between analysts and shifts.
Program managers
Manage batch throughput in labs
Higher throughput with traceability
Batch management organizes inputs and outputs so teams can process runs without ad hoc spreadsheets.
Best for: Fits when labs run frequent sieve stacks and need traceable, standardized gradation reports.
Mecmesin Emperor
vertical specialistEmperor controls Mecmesin test systems and records, analyzes, and reports laboratory measurement data.
Instrument-linked run processing that converts sieve stack measurements into standardized gradation report packages with consistent calculations.
Emperor supports the full path from sieve stack configuration through run data ingestion to automated production of a gradation report. The workflow is designed around typical sieving lab steps such as recording sample mass, computing per-mesh results, and validating aperture-to-mesh mappings across test runs. Report outputs are structured enough for compliance-driven review, which reduces the manual rework commonly seen when lab staff export raw tables to spreadsheets. A consistent configuration approach also makes it easier to reproduce the same stack configuration across multiple batches.
A key tradeoff is that Emperor’s value is strongest when sieving data comes from the supported Emperor measurement flow, while fully custom import and transformation pipelines are less central than in general-purpose data tooling. Emperor works best when teams need repeated throughput from routine dry sieving tests into standard report formats like gradation report packages, not when analysts need a highly flexible Python-first workflow. For environments already standardized on ASTM D6913 or ISO-style reporting, Emperor’s structured outputs reduce the gap between lab results and documentation.
- +Batch workflow ties sieve stack setup to automated calculations and reports
- +Outputs are structured for consistent engineering review across runs
- +Measurement records support traceable repeatability for lab execution
- +Designed around sieve test throughput instead of manual spreadsheet handling
- –Custom data transformation needs can exceed what the UI-centric workflow offers
- –Integration breadth depends on instrument and file pathways rather than open-ended ingestion
- –Governance and role-based administration controls are not its primary design focus
- –Advanced scripting flexibility is limited compared with Python-led analysis
Materials lab engineers
Batch routine aggregate gradations
Fewer manual calculations and edits
Geotechnical quality teams
Document and review sieve results
More consistent documentation
Show 1 more scenario
Field test supervisors
Standardize stack configuration
Reduced variability between runs
Applies repeatable sieve stack order and sample mass handling across batches.
Best for: Fits when labs run repeated sieving tests and need standardized gradation report outputs.
Microtrac MRB
enterpriseParticle characterization instruments including sieve analysis modules.
Sieve stack driven calculations automatically generate cumulative passing curves and percent retained summaries tied to a single run.
Microtrac MRB provides a structured workflow for sieve stack configuration, where mesh size and stack order drive downstream calculations for particle size distribution outputs. Results can be entered as percent retained or fraction weights, and the software computes cumulative passing and gradation curve outputs for inclusion in gradation reports. The reporting layer formats outputs around sieve analysis deliverables used in geotechnical and aggregates documentation. MRB also supports practical lab operations by keeping run inputs and derived results linked, reducing manual copy steps.
A tradeoff is that MRB centers on sieve-analysis data handling rather than general-purpose scripting, so custom analysis logic may require exporting data to other tools for extended modeling. MRB fits well when multiple operators must run the same sieve stack and produce consistent gradation reports for compliance workflows such as AASHTO T 27 or internal acceptance tests. It is less ideal when teams already have full automation in Python or MATLAB and only need flexible charting without a guided run model.
- +Guided sieve stack configuration ties mesh order to calculated gradation outputs
- +Built-in cumulative passing curve generation from sieve fractions and weights
- +Run capture keeps percent retained inputs linked to report-ready results
- +Report formatting reduces manual rework across repeated sample runs
- –Custom computation logic beyond the standard workflow needs export to external tools
- –Automation relies on MRB workflow configuration rather than fully programmable analysis code
- –Bulk processing flexibility can be limited compared with code-first pipelines
- –Import formats for sieve shaker data may require preprocessing into MRB-friendly fields
Geotechnical lab technicians
Produce gradation reports from sieve fractions
Fewer transcription and calculation errors
Quality managers
Standardize sieve stack reporting formats
Repeatable documentation across teams
Show 1 more scenario
Materials engineering teams
Compare aggregate gradation batches
Clear pass or fail evidence
Engineers generate percent retained and cumulative summaries for side-by-side batch comparison in reports.
Best for: Fits when labs need consistent sieve-based gradation reports across repeated operators and stack configurations.
Malvern Panalytical Mastersizer
enterpriseLaser diffraction particle sizing software supporting sieve correlation.
Run-level measurement outputs map directly into analysis exports used for cumulative passing curve review and sieve-style validation.
Malvern Panalytical Mastersizer performs particle size distribution measurements and generates gradation outputs suitable for sieving-style reporting workflows. The measurement pipeline supports controlled optics, repeatable runs, and exportable analysis artifacts used to support mass balance verification against sieve stack results.
- +Instrument-to-report workflow keeps particle size distribution outputs consistent across runs
- +Export formats support downstream gradation report assembly and curve review
- +Repeatable acquisition settings reduce variability when comparing batches
- +Traceable run-level outputs support auditing of sieve-style comparisons
- –Best sieve-analysis fit requires deliberate calibration and method alignment
- –Automation and API access depend on the surrounding lab software integration
- –Complex sample prep and measurement settings can slow early adoption
- –Dataset merging across instruments may require custom lab workflow handling
Materials testing labs
Export Mastersizer results for sieve reports
Faster, consistent documentation
QA compliance teams
Verify mass balance against sieve stacks
Audit-ready traceability
Show 1 more scenario
R&D process engineers
Compare optics across measurement runs
Comparable distributions
Integrates with external lab systems for data capture and run traceability during cross-technique comparisons.
Best for: Fits when geotechnical and materials labs need repeatable particle size distribution exports for sieve-style gradation review and traceable run comparisons.
Laboratory Sieve Analysis Software by Global Gilson
vertical specialistSoftware and data interfaces for Gilson sieve shakers and gradation testing workflows.
Sieve shaker data import paired with calculation checks that preserve sieve stack configuration through report output.
Laboratory Sieve Analysis Software by Global Gilson targets geotechnical and aggregate labs that need repeatable gradation reports from sieve stack measurements. It supports importing sieve shaker data and calculating percent retained across the stack, then generating a standard gradation report for review and release workflows.
- +Generates consistent gradation report outputs from imported shaker results
- +Calculations based on percent retained across the configured sieve stack
- +Supports sieve stack order and mesh size configuration for traceable runs
- +Exports particle size analyzer friendly result tables for downstream checks
- –Workflow depends on correct stack configuration before calculations
- –Automation is oriented around sieve data import rather than wider particle analytics
- –Limited support for wet sieving workflows compared with multi-technique analyzers
- –Report customization is constrained versus fully scripted notebook pipelines
Geotechnical lab managers
Generate gradation reports from stack data
Repeatable report production
Field materials testing staff
Import shaker data for faster processing
Less manual transcription
Show 1 more scenario
Construction quality teams
Track mesh set configuration and results
Tighter result accountability
Maintains traceability of stack configuration and calculations tied to each gradation output.
Best for: Fits when labs want standardized gradation report generation with sieve shaker imports and controlled stack setup.
Sympatec
enterpriseParticle measurement systems with integrated sieve analysis software.
End-to-end lab workflow integration that carries particle size results into standardized gradation reporting artifacts.
Sympatec focuses on particle size measurement and analysis workflows that produce lab-ready outputs for geotechnical and aggregate contexts.
- +Lab-grade gradation reporting tied to instrument workflow outputs
- +Repeatable run configuration supports consistent sieve stack documentation
- +Import pipeline reduces manual retyping of sieve shaker results
- +Export formats support downstream compliance documentation
- –Sieve-only workflows can feel heavier than lightweight sieve calculators
- –Automating complex grading logic needs careful configuration discipline
Aggregate characterization teams
Standardize gradation documentation outputs
Uniform lab outputs
Geotechnical QA reviewers
Produce review-ready gradation summaries
Cleaner reviewer handoff
Show 1 more scenario
Lab operations coordinators
Reduce rework between runs
Lower revision rate
Keeps results formatted consistently so repeat tests generate comparable gradation documentation.
Best for: Fits when lab teams need sieve reporting integrated with instrument-based particle sizing workflows.
SieveWare
vertical specialistSieveWare records sieve analysis data and produces particle size distribution reports.
Report generation that turns sieve stack inputs into gradation outputs like cumulative passing curves with fewer spreadsheet steps.
SieveWare by endecotts.com targets sieve analysis workflows where repeatable calculations and traceable lab outputs matter. It supports data capture for sieve stack runs and generates standard gradation outputs such as cumulative passing curves and percent retained tables.
- +Clear gradation report outputs built from sieve stack inputs
- +Consistent mass balance style calculations for percent retained and cumulative passing
- +Export-oriented workflow designed for lab documentation handoff
- +Workflow fit for dry sieving datasets used in compliance checks
- –Limited automation depth compared with lab-centric systems used for multi-method testing
- –Requires careful setup of sieve stack order to avoid incorrect curve generation
- –API and integration surface are not positioned for engineering pipelines
- –Less suited to programmatic analysis than MATLAB or a Python notebook flow
Cement and aggregate labs
Capture shaker runs for gradation tables
Structured gradation outputs
Compliance engineers
Compare results to acceptance envelopes
Fewer calculation mistakes
Show 2 more scenarios
Lab documentation teams
Export lab-report-ready curves
Quicker report assembly
Organizes exports in formats aligned to lab documentation so results transfer cleanly into reports.
Site testing supervisors
Standardize stack-based calculations
More comparable runs
Keeps calculation consistency across repeated sieve stack sessions for comparable results.
Best for: Fits when lab teams need repeatable sieve stack calculations and report-ready outputs for engineering review.
Retsch
enterpriseSieve shaker manufacturer offering evaluation software for sieve analysis.
Run capture that stays tied to the instrument measurement session, including sieve stack context, for consistent gradation report generation.
Retsch is differentiated by its tight coupling between Retsch particle-size hardware and lab workflows for sieve analysis, rather than treating sieving as a generic upload-and-chart task. The software side supports building a sieve stack, capturing shaker runs, and generating gradation-style outputs that labs can use for reporting and compliance checks. Automation depth shows up in instrument-connected data capture, repeatable run import, and standardized outputs across measurement sessions.
- +Instrument-connected data capture reduces manual transcription errors during sieve runs
- +Sieve stack setup matches lab practice for consistent stack configuration across projects
- +Exports support downstream lab reporting and particle size distribution workflows
- +Run records help keep measurement context attached to each gradation report
- –Non-Retsch instrument workflows require extra handling for consistent data import
- –Complex reporting requires careful configuration to match a lab’s gradation report format
- –Throughput depends on instrument capture reliability and data transfer stability
- –Limited scripting depth makes custom analysis less straightforward than code-first options
Retsch-instrument labs
Build sieve stacks and capture shaker runs
Consistent session data
Quality assurance reviewers
Generate standardized gradation outputs per session
Reduced review effort
Show 1 more scenario
Test lab automation teams
Automate instrument-connected data capture
Lower transcription risk
Uses instrument-connected import paths to reduce manual transfers from shaker measurements to reporting.
Best for: Fits when labs already run Retsch sieving hardware and need repeatable gradation reporting with minimal manual cleanup.
Particle Expert
vertical specialistParticle size analysis software that supports sieve analysis workflows with result management and reporting.
Configurable sieve stacks plus calibration inputs drive repeatable percent retained and cumulative curve outputs without spreadsheet reshaping.
Particle Expert from bettersizeinstruments.com targets sieve analysis workflows with file-based ingestion, a stack-aware calculation pipeline, and export outputs for gradation reporting. It focuses on converting sieve shaker or manual result tables into consistent distributions and cumulative curves while tracking mass-balance inputs.
- +Stack-aware calculations reduce errors when sieve ranges change per test
- +Gradation outputs stay consistent across batches through reusable configurations
- +Supports common sieve analysis reporting structures for lab documentation
- +Exports align with downstream lab workflows and document generation
- –Automation and API surface are limited compared with script-first Python options
- –Wet sieving workflows require more manual preparation than dry-sieving flows
Geotechnical compliance labs
Ingest sieve and shaker files for reporting
Less spreadsheet work
QA repeatability analysts
Maintain configurable sieve stacks and calibration
More repeatable outputs
Show 2 more scenarios
Aggregates testing teams
Track mass-balance inputs during runs
Better traceability
Tracks mass-balance inputs so sieve-derived distributions connect back to measurement inputs.
Laboratory report coordinators
Export standard cumulative curve outputs
Cleaner report formatting
Exports gradation-ready cumulative views aligned to standardized reporting for compliance checks.
Best for: Fits when labs need repeatable sieve analysis reporting with configured sieve stacks and consistent exports.
Autosoft
vertical specialistTest control and data acquisition software used with materials testing equipment including sieve shaker setups.
Configured sieve stack templates drive consistent ordering and reporting outputs across projects.
Autosoft ingests sieve stack results from geotechnical and materials testing workflows and generates gradation outputs and reports. Its core value sits in repeatable parsing of shaker and manual measurements into consistent gradation curves, plus exportable tables for compliance-oriented documentation.
- +Report generation ties sieve results to cumulative passing outputs
- +Batch import reduces manual retyping from shaker logs and spreadsheets
- +Configurable sieve stack handling supports consistent mesh ordering
- +Exports produce lab-ready tables for documentation workflows
- –Wet and dry mode workflows require disciplined input setup
- –Integration depth is limited outside the sieve and gradation reporting scope
Materials labs
Parse shaker and manual results into curves
Faster turnaround
Compliance documentation teams
Generate exportable gradation report tables
Consistent submissions
Show 1 more scenario
Test lab administrators
Standardize stack configuration and formats
Lower variation
Applies configuration and workflow controls to enforce consistent reporting formats across projects.
Best for: Fits when lab teams need standardized sieve report output with batch imports and controlled stack configuration.
Conclusion
After evaluating 10 sieve analysis software, Particle Technology Labs PTL-LIMS 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.
Frequently Asked Questions About Sieve Analysis Software
How do sieve analysis tools convert sieve shaker counts into percent retained and cumulative passing curves?
Which tool best supports calibration-aware sieve stack provisioning for traceable apertures?
When labs need instrument-linked capture, which software keeps run context tied to the capture session?
What breaks if sieve stack order or fraction mapping is configured incorrectly in these tools?
How do tools handle imports from sieve shaker systems versus manual entry workflows?
Which option is strongest for API and automation patterns around repeatable lab workflows?
How do sieve analysis tools support admin controls and governance across multiple lab projects or operators?
What integration paths exist for cross-technique lab workflows and data exports?
When should a lab choose a file-based export workflow instead of a tight instrument workflow?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
How to Choose the Right Sieve Analysis Software
What separates sieve analysis software is how it turns your sieve results into a trustworthy output: the way it handles the math and reporting in Result processing, the automation around importing and sorting data in Data import workflow, and how consistently it reproduces the same curves and tables in Report outputs. These choices affect whether later edits stay auditable and defensible.
Result processing accuracy
Why it matters
Result processing accuracy determines whether the computed fractions and curves match your input and the expected calculations for sieve analysis. If the tool recomputes differently each time, your grading decisions can shift.
How to check
Run the same sample twice with a small change (e.g., corrected mass entry) and compare the outputs line-by-line. Check that it reports percent retained and the final cumulative view consistently with the same calculation basis across sessions.
Data import workflow for sieve tables
Why it matters
A strong Data import workflow for sieve tables reduces manual transcription errors and keeps your raw entries tied to outputs. With high-throughput labs, misaligned columns or units quickly distort the distribution.
How to check
Use a sample spreadsheet or CSV in the demo and import it. Ask the vendor to show how it maps columns to required fields, validates missing values, and flags inconsistent entries.
Report outputs for curves and tables
Why it matters
Report outputs for curves and tables matter because sieve analysis is often reviewed as both a visual curve and the underlying numbers. Buyers need the output to be reproducible and exportable for internal review.
How to check
Generate a report from the imported data and verify the presence of the key tables and the main curve view in one package. Then export in the formats offered (e.g., PDF and spreadsheet) and confirm the numbers match the on-screen tables.
Standard-specific configuration
Why it matters
Standard-specific configuration helps labs keep grading outputs aligned to the conventions they use, especially when projects mix method variants. Without it, users end up forcing outputs through manual workarounds.
How to check
In the demo, switch between available method/standard modes and re-run the same dataset. Ask what changes in the output and verify it affects only the intended parts of the calculations and formatting.
Audit trail for input and edits
Why it matters
An audit trail for input and edits is critical when you need to explain why a report changed after corrections. It also helps teams review who adjusted entries and which recalculations occurred.
How to check
Make a small edit to an imported value, regenerate the report, and inspect whether the system records what changed. Ask how it labels versions and whether prior results remain accessible for comparison.
Automation and API surface
Why it matters
Automation and API surface reduce turnaround time when projects pull data from other lab workflows. Buyers often want to generate outputs in a consistent way rather than repeating clicks.
How to check
Ask for an example of an API call or automation job that imports data and triggers report generation. If an API isn’t shown, test whether the tool supports repeatable batch runs with the same settings on multiple files.
Red flags
- Outputs change after small edits without a clear recalculation log
- Imports accept files but silently mismatch columns or units
- Reports export curves that don’t match the underlying tables
Fit by situation
- If your team frequently corrects input masses after review, prioritize Audit trail for input and edits.
- If you process many sieve spreadsheets per week, prioritize Data import workflow for sieve tables.
- If projects require consistent deliverables across methods, prioritize Standard-specific configuration.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
Keep exploring
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
Chemicals & Industrial Materials alternatives
See side-by-side comparisons of chemicals & industrial materials tools and pick the right one for your stack.
Compare chemicals & industrial materials tools→