USDA Pesticide Data Program search and data download guide
The USDA Pesticide Data Program tracks food residues. Learn how to search its database, export CSV data and interpret findings against US tolerances.
The USDA Pesticide Data Program (PDP) is the United States Department of Agriculture's pesticide residue testing program. It monitors residues in food so EPA can assess dietary exposure. Its PDP database lets you select foods, pesticides, and years, then export PDP data as CSV.
For a food compliance or quality team, the first decision is which results to include. But a positive-only export answers a different question from one that includes non-detects. Neither a detection nor a historical database flag, on its own, establishes current compliance or health risk. USDA's search instructions explain the result options. EPA explains the tolerance and risk-assessment framework.
What the USDA Pesticide Data Program tests
USDA's Agricultural Marketing Service runs PDP with state agriculture departments and other federal agencies. The AMS overview says the program pays particular attention to foods eaten by infants and children. The database background includes fresh and processed produce, baby food, grains, nuts and dairy in the program's historical coverage. Those are examples, not a list of foods tested every year.
Processing forms matter. The commodity selector lists apples, apple juice and apple sauce separately. Select the form that matches your question rather than treating each as the same commodity.
PDP began in 1991, but its searchable database starts in 1994. Earlier years are excluded because non-detects were not captured before 1994. As checked on 8 November 2026, the online database offered data for 1994–2024, and 2025 data was still awaiting official release. That range describes searchable data, not the publication date of the newest annual report.
PDP data can inform a US dietary-exposure question, but a result here is not pesticide application or use data and it is not proof of a UK residue limit. For compliance, EPA sets tolerances or exemptions, while FDA tests domestic and imported food for compliance. EPA says USDA notifies FDA when its data collection identifies tolerance violations. A PDP monitoring result is not itself an FDA enforcement outcome.
How to search the PDP database and export data
Use the PDP database search for a filtered selection. USDA's Help page describes these steps.
- Select the commodities. Choose all commodities or the foods and processing forms you need.
- Select the pesticides. Use all pesticides or a defined selection.
- Select the calendar years. Record them with your export so the scope remains clear.
- Choose an output. Options are Analytical Results, Sample/Results, Summary of Findings, Summary of Findings by Origin and Summary of Findings by Claim.
- Choose the result preference for Analytical Results or Sample/Results. The options are Positive Detects Only, All Positive Detects + Non-Detects, or Presumptive Tolerance Violations Only.
- Run the search. Use the boxes below column names if you need to filter the displayed results.
- Select Export to Excel. Despite that label, USDA says the exported file is CSV, not an XLSX workbook.
Save the commodity forms, pesticides, years, output and result preference with the file. Another analyst can then repeat the query without guessing what the export includes.
The app also links a Data Dictionary and User Guide. Consult those documents before interpreting coded fields or combining files.
How to read PDP annual summaries
Start with the AMS annual-summary index and select the reporting year you need. Before using a figure in a compliance report, check what it counts.
- Confirm the sampling year. Don't substitute the publication year when describing when samples were collected.
- Check the foods and processing forms tested that year. The database's all-years commodity list is not an annual sampling list.
- Separate samples from findings. One sample can contribute multiple analytical findings. USDA reports 335,940 samples and over 52 million findings for 1994 through 2024, so those totals are not interchangeable.
- Check whether the denominator includes non-detects. A positive-only export cannot establish the detection rate among all tests.
- Retain the word "presumptive" when discussing the database's tolerance-violation category. Don't present that category as a final enforcement decision.
- Read the analytical documentation and detection limits before interpreting non-detects. Don't label food "pesticide-free" on that basis.
Those distinctions come from USDA's database background, USDA's search instructions and EPA's explanation of agency roles.
A tolerance is the maximum amount of a pesticide legally allowed to remain in or on food. US tolerances apply to imported food as well as food grown domestically. Some pesticides have exemptions, so a missing numerical limit does not settle legality. For a current US compliance decision, consult the applicable tolerance provisions, including 40 CFR Part 180, rather than relying on a historical flag.
Detection counts alone also do not quantify health risk. EPA considers toxicity and exposure in its safety assessment, with particular consideration of infants and children. Use that framework rather than ranking foods by the number of chemicals detected.
Where to download annual PDP files
For a full annual package, start at AMS's PDP bulk-data page. Select the required reporting year and follow the instructions bundled with that download. AMS also provides database download instructions.
Keep this route separate from a filtered online CSV export. Check the selected year's documentation before treating either file set as a substitute for the other. For year-specific findings, use the annual summary alongside the data rather than substituting a database total for the report's explanation.
RegAffairs AI's answer on the USDA Pesticide Data Program covers the program and its download routes.