Understanding Cronometer's Food Databases
Cronometer uses more than one food data source when tracking your nutrition. The CRDB is one part of a system. The app's commitment to accurate data is a key feature. This is achieved by using multiple sources. Understanding each database helps optimize your logging for complete nutritional insights.
The Role of the Cronometer Community Database (CRDB)
The CRDB is important for Cronometer, allowing a dynamic and growing database of packaged and branded foods. User submissions for packaged foods are routed into the CRDB. Each entry in Cronometer's CRDB is reviewed and edited by a curation team. This makes sure the data logged is based on the food manufacturer's nutrition label.
CRDB entries often contain less micronutrient information compared to other data sources. A CRDB entry for cereal might show macronutrients and some vitamins, but would not show all 70+ nutrients Cronometer can track. The CRDB is best for logging the nutritional information on a product's packaging.
Other Key Data Sources
Cronometer uses other databases that provide more detailed, lab-analyzed data for generic foods. This is where you can find the most complete nutrient information.
- NCCDB (Nutrition Coordinating Center Food & Nutrient Database): The NCCDB is considered the gold standard for research-grade food data. It provides a comprehensive profile of over 70 nutrients for many generic foods. Using the NCCDB entry for a raw almond will give you the most detailed nutrient breakdown.
- USDA (United States Department of Agriculture National Nutrient Database): The USDA provides a reliable database of nutrient data, particularly for generic and cooked foods. Using USDA data is recommended for cooked meats, as it contains specific information on various cooking methods.
- Nutritionix: This database powers Cronometer's barcode scanning for branded products. These entries, like those in the CRDB, reflect only what is on the manufacturer's label and are not as comprehensive as lab-analyzed entries.
CRDB vs. Lab-Analyzed Databases: A Comparison
Here's how the CRDB compares against the NCCDB or USDA for different food logging.
| Feature | CRDB (Cronometer Community Database) | NCCDB/USDA (Lab-Analyzed Databases) |
|---|---|---|
| Data Origin | User-submitted, verified by Cronometer's team | Lab-analyzed, research-grade data |
| Food Type | Primarily branded and packaged products | Generic, whole foods (e.g., raw fruits, vegetables) |
| Nutrient Profile | Limited to information on the manufacturer's label | Comprehensive, including all 70+ trackable nutrients |
| Primary Use Case | Accurately logging specific packaged items with known labels | Detailed tracking of micronutrients and whole food intake |
| Accuracy Concern | Missing some micronutrients not on the label | Generally highest accuracy, minimal concerns if the food is a generic type |
Best Practices for Accurate Tracking
To get the most out of Cronometer and ensure your data is as accurate as possible, follow these best practices:
- Use the CRDB for branded foods. Use the CRDB entry (via barcode or search) to get the information from that manufacturer's label.
- Opt for NCCDB/USDA for whole foods. For ingredients like a raw apple or plain chicken breast, search for the generic version and select the NCCDB or USDA entry. This gives you the most complete micronutrient profile.
- Weigh your food. Weighing your food is the most accurate method for portion sizes, regardless of the data source.
- Don't worry about missing data. If a CRDB entry lacks data for a particular nutrient, it means the manufacturer did not list it on the packaging. The CRDB will not fill in gaps with assumptions to maintain data integrity.
Conclusion: CRDB is a Curated, Not Crowdsourced, Database
In summary, CRDB is the company's community-driven database of user-submitted branded and packaged foods. The verification process by Cronometer's team prioritizes accuracy. CRDB entries reflect the information from a product's label. Using the comprehensive NCCDB and USDA sources for generic foods allows you to achieve the detailed, lab-analyzed nutritional tracking that Cronometer is known for. A balanced approach using both data types will give you the most accurate picture of your dietary intake.
How to Publish a Food to CRDB
Submitting a custom food to the CRDB is possible, but it requires the food to be a common, packaged, store-bought, or restaurant item with verifiable nutrition information. You cannot submit homemade recipes or whole foods. This ensures the database stays focused on branded products with nutrition facts. The Cronometer curation team reviews the entry before it becomes public. The support articles on Cronometer's website provide instructions.
