Turkey thawing calculator

Enter twelve pounds with refrigerator and you get two point four days (fifty-seven point six hours); enter the same weight with cold_water and you get six hours. Zero, negative, missing, or non-numeric weight fails with a clear invalid_input error instead of inventing a thaw window.

Refrigerator versus cold-water turkey thawing, and the rates this tool uses

You send a positive weight in pounds and a method of refrigerator or cold_water; the response echoes the cleaned weight, the canonical method, a primary duration with a unit of days for the fridge path or hours for the bath path, plus thaw_hours, thaw_days, hours_per_pound, a formula string, and a short human message. It does not model microwave defrost cycles, ambient kitchen counters, stuffed cavities, brining time after thaw, or variable fridge setpoints, because those methods follow different time scales and safety rules. When validation fails you receive invalid_input with a field-aware message and the request is not charged.

How weight and method are read and how duration fields are produced

Embedded spaces, hex prefixes, empty strings, and non-numeric tokens are rejected so a bad cell does not become a silent wrong schedule. Negative zero collapses to plain zero before the positive check, and magnitudes above the documented ceiling are refused. The preferred field is weight, a finite number of pounds strictly greater than zero. Aliases weight_lb, pounds, lb, w, and mass_lb map to the same value so spreadsheets, query strings, and typed forms can reuse the contract without renaming columns. The value may arrive as a JSON number or as a numeric string; optional leading plus signs and scientific notation are accepted when they parse as finite decimals. Method is optional and defaults to refrigerator when omitted; send cold_water when you need the fast bath. Canonical method ids are refrigerator and cold_water. Common aliases such as fridge, refrigeration, cold, water, cold-water, bath, and sink are accepted and normalized before arithmetic runs. After validation, the refrigerator path multiplies weight by twenty-four divided by five for thaw_hours and divides weight by five for thaw_days, then sets duration to those days with duration_unit days. The cold-water path multiplies weight by one half for thaw_hours, divides that result by twenty-four for thaw_days, and sets duration to the hours with duration_unit hours. Both paths still return thaw_hours and thaw_days so a client can display either unit without a second request. Example checks you can pin in tests: twelve pounds refrigerator yields duration two point four days and fifty-seven point six hours; sixteen pounds cold_water yields duration eight hours; twenty pounds refrigerator yields four days and ninety-six hours. The free browser path and the priced API path share the same solve module, so a meal-prep script and this landing page never disagree on arithmetic. Pair the estimate with your own calendar buffer if you want an extra day for brining or late grocery delays—the endpoint only computes the fixed-rate thaw window, not cooking time, stuffing, or doneness.

Where a turkey thawing estimate fits in cooking and software

On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split—free interactive exploration and a priced, identical API—matches the rest of the tier-A catalog and lets you move from a kitchen demo to an automated pipeline without changing the mathematical result. Keep this endpoint when the search intent is turkey thawing across fridge and cold-water methods; use a dedicated oven, recipe-scale, or unit-conversion tool when you need roasting temperature, ingredient scaling, or side-dish measures rather than thaw duration.