Days until December
From 25 July 2026 there are 129 days until 1 December. Enter any date and get the full days left until the next first of December, which moves to the following year once December has begun. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Date
- 2026-07-25
- Year
- 2,026
- Month
- 7
- Day
- 25
- Target date
- 2026-12-01
A days-until-December calculator answers a seasonal planning question people type every autumn and winter: from a given calendar day, how many full days remain until the next first of December? Paste an ISO date in year-month-day form, and this tool returns the remaining day count until December first of the current year if that date has not yet arrived, or until December first of the following year if the given day already sits after December first. When the input is December first itself the remaining count is zero.
What “days until December” means on the Gregorian calendar
An ISO calendar date is written as four digits for the year, a hyphen, two digits for the month, another hyphen, and two digits for the day of the month—for example twenty twenty-six dash zero seven dash twenty-five. That form is unambiguous across locales that write month-first or day-first in everyday prose, which is why APIs and databases prefer it. Underneath, the Gregorian calendar still rules month lengths: thirty or thirty-one days for most months, February with twenty-eight days in a common year and twenty-nine only in a leap year.
A leap year is every year divisible by four, except century years that are not divisible by four hundred. Days until December, on this page, means whole civil days from the given date until the next first of December. If the given day is in January through November, the target is the first of December of that same year.
If the given day is the first of December, the remaining count is zero because the horizon has already arrived. If the given day is the second of December through the thirty-first, the next first of December belongs to the following year, so the count crosses the year boundary and includes the rest of December plus January through November of the next year. That definition matches everyday language for holiday countdowns without inventing a year-end horizon of thirty-one December and without asking the caller to name a free-form event date.
Where a December countdown earns its keep
Retail and hospitality teams use a days-until-December calculator to size Black Friday, Advent, and winter-travel campaigns against a fixed first-of-December horizon instead of a generic event date they would have to type twice. School offices and municipal boards pin winter-break banners and lighting-ceremony notices to the same integer so reprints stay identical. Travel agents and ski-lodge operators convert a booking as-of date into remaining days before December first when packages open.
Parent pages and in-store kiosks can run the free in-browser tool without installing a date library. Keep expectations honest: this capability measures Gregorian civil days from one explicit date to the next first of December; it does not skip weekends as business days, load public holiday calendars, convert lunar festivals, default the date from the server clock, or count to thirty-one December.
Pair it with a days-left-in-the-year tool when the search is year-end remainder, with a calendar countdown when the event is an arbitrary day, and with a birthday helper when the date repeats every year.
What you can do with it
Holiday and winter-campaign planning
Turn a planning date into remaining civil days until the next 1 December so Advent, lighting, and winter-sale calendars stay identical in every reprint.
Travel and lodging open windows
Convert a booking as-of date into days before December first when ski, cruise, or city-break packages open for the winter season.
FAQ
How do I compute days remaining until December?
Send a valid ISO calendar date as date (YYYY-MM-DD).
What happens if the date is 1 December?
The target is that same 1 December, not the following year.
What if the date is after 1 December?
The target rolls to 1 December of the following year. For example, 15 December 2026 counts days until 1 December 2027.
Why count to 1 December and not to the end of the year?
Because the first of December is the fixed start for Advent, holiday campaigns and winter travel packages. If you want the days left until the year ends, use a days-left-in-the-year tool instead.
Does a leap year change the count?
Yes, when the span includes February of a leap year, because that February has 29 days. This happens for dates early in a leap year and for December dates that roll into one.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/life/days-until-december \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"date":"2026-07-25"}'const res = await fetch("https://api.kit.forhosting.com/life/days-until-december", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"date": "2026-07-25"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/life/days-until-december",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"date": "2026-07-25"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/life/days-until-december", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"date":"2026-07-25"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"date":"2026-07-25"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/life/days-until-december", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"date": "2026-07-25"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "life.days_until_december",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
year_min | 1 |
year_max | 9999 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Invalid strings—wrong shape, impossible months, or a twenty-ninth of February outside a leap year—are rejected with a clear invalid_input error instead of a silent wrong answer.
Input contract, response shape, and error behaviour
The value must match the exact pattern of four digits, hyphen, two digits, hyphen, two digits, and must represent a real Gregorian day in the inclusive year range from one through nine thousand nine hundred ninety-nine. A date after the first of December in year nine thousand nine hundred ninety-nine is also rejected, because the next first of December would leave the four-digit year range. Send a JSON body with one required string field named date, which may also be supplied under the aliases iso_date, value, or day. On success the response echoes the canonical date string plus year, month, and day as numbers, sets target_date to the ISO string of the next first of December and target_year to that year, sets days and days_remaining to the same non-negative integer count of full civil days, sets is_december_first true only when the count is zero, sets leap_year from the input year, and includes a short formula string plus a human message. Failed validation—missing field, non-string type, bad shape, out-of-range year, impossible month or day, or a non-leap twenty-ninth of February—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item.
Where a December countdown earns its keep
Call the prepaid API when notification pipelines, print shops, or classroom tools need a stable contract under KIT balance at $0.002 per successful item; validation failures never consume balance after the engine rejects the request.
Integration use cases
Countdown fixtures and classroom checks
Pin leap-year and December-first edge cases in tests and homework so the remaining-day integer never depends on a host clock or timezone.
Technical questions
Which dates are rejected?
Missing or empty date, a string that is not YYYY-MM-DD, an impossible month or day, and 29 February in a non-leap year all fail with invalid_input and are not billed.
What does the days until December calculator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.