Gregorian to Indian Saka calendar converter
Type a Gregorian date and get its place in India's official Saka calendar: 15 August 1947 is 24 Shravana 1869. The result also gives the month number, the day of the Saka year and whether Chaitra has 31 days. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Date
- 1947-08-15
- Gregorian
- 1947-08-15
- Saka year
- 1,869
- Saka month
- 5
- Saka month name
- Shravana
The Indian National Calendar, also called the Saka calendar, runs in parallel with the Gregorian calendar for official Indian government use. New Year is Chaitra 1, fixed to twenty-two March in common Gregorian years and twenty-one March in Gregorian leap years, and the Saka year number is the Gregorian year minus seventy-eight from that New Year onward. This converter accepts a single explicit Gregorian ISO date, interprets the year, month, and day digits in UTC with no timezone shift, and returns the matching Saka year, month index, English month name, day of month, a ready-to-display Saka date string, whether Chaitra has thirty-one days in that Saka year, and the ordinal day of the Saka year.
How the Indian National Saka calendar maps onto Gregorian dates
The Indian National Calendar is a civil solar calendar adopted for official use alongside the Gregorian system. Its twelve months begin with Chaitra and end with Phalguna. Month lengths are fixed by statute-style civil rules rather than by traditional lunar observation: Chaitra has thirty days in a common Saka year and thirty-one days when New Year falls inside a Gregorian leap year; Vaishakha, Jyeshtha, Ashadha, Shravana, and Bhadra each have thirty-one days; Ashwin, Kartika, Agrahayana, Pausha, Magha, and Phalguna each have thirty days.
Chaitra 1 is locked to twenty-two March of the corresponding Gregorian year, or to twenty-one March when that Gregorian year is a leap year under the usual divisible-by-four, century, and four-hundred rules. From Chaitra 1 of Gregorian year Y through the thirty-first of December of Y, the Saka era year equals Y minus seventy-eight. From the first of January of Y until the day before Chaitra 1, the date still belongs to the previous Saka year, so the year number is Y minus seventy-nine.
Those two epoch rules alone determine which Saka year owns any civil Gregorian day. Once the New Year Gregorian date is known, the converter counts whole days from that New Year to the input date using an integer Julian Day Number difference, then walks the twelve fixed month lengths until the remaining offset falls inside a single month. The month index is one-based, the day is one-based, and the English month name is taken from the standard modern list Chaitra through Phalguna.
Because every step is arithmetic on the input digits only, the same ISO string always yields the same Saka fields, which is essential for goldens, automated tests, and SEO landings that show live examples.
How to enter the date and read the result
The value must be a Gregorian civil date in ISO form with a four-digit year, a two-digit month, and a two-digit day separated by hyphens, for example nineteen forty-seven hyphen zero eight hyphen fifteen. Month must lie between one and twelve. Day must lie between one and the true length of that Gregorian month, including twenty-nine February only in leap years; an impossible day such as the thirty-first of April fails validation and is not billed.
There is no direction switch and no reverse conversion in this capacity: it is deliberately a single-intent Gregorian-to-Saka landing. Optional fields are omitted rather than set to null. Classic reference checks include Independence Day fifteen August nineteen forty-seven mapping to twenty-four Shravana of Saka year eighteen sixty-nine, and Republic Day twenty-six January nineteen fifty mapping to six Magha of Saka year eighteen seventy-one.
Where a Gregorian to Saka converter earns its keep
Government forms, gazette footnotes, and school textbooks in India routinely print both Gregorian and Saka dates on the same line. Newsrooms and archival projects that tag historical events by Saka year can batch-convert ISO dates without standing up a calendrical library of their own. Exam platforms and civil-service prep apps need a deterministic oracle that treats leap-year Chaitra correctly so March twenty-one and March twenty-two never swap New Year by accident.
Failed validation does not consume balance.
What you can do with it
Official dual-date documents
Print Saka year, month, and day next to a Gregorian ISO date on forms, certificates, and gazette-style pages with a stable civil mapping.
Education and exam prep
Let learners convert sample civil dates—including leap-year New Year on twenty-one March—and check answers against a deterministic Saka oracle.
News and archive tagging
Batch-label historical and current events with Saka era fields for India-facing timelines without shipping a full calendar library.
FAQ
When is Saka New Year (Chaitra 1)?
Chaitra 1 is 22 March in common Gregorian years and 21 March in Gregorian leap years. From that day the Saka year equals the Gregorian year minus 78.
What is the Saka year for a January date?
Dates from 1 January until the day before Chaitra 1 still belong to the previous Saka year, so the year number is the Gregorian year minus 79.
Does the converter use my local timezone?
No. Only the year, month, and day digits of the ISO string are used, interpreted as a pure civil date in UTC with no clock or timezone shift.
How long are the months of the Saka calendar?
Chaitra has 30 days, or 31 in a Saka leap year. Vaishakha, Jyeshtha, Ashadha, Shravana and Bhadra have 31 days each, and the last six months, from Ashwin to Phalguna, have 30.
When is a Saka year a leap year?
When its New Year, Chaitra 1, falls in a Gregorian leap year. Chaitra then has 31 days, and New Year moves from 22 March to 21 March.
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/date/gregorian-to-saka \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"date":"1947-08-15"}'const res = await fetch("https://api.kit.forhosting.com/date/gregorian-to-saka", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"date": "1947-08-15"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/date/gregorian-to-saka",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"date": "1947-08-15"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/date/gregorian-to-saka", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"date":"1947-08-15"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"date":"1947-08-15"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/date/gregorian-to-saka", 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": "1947-08-15"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "date.gregorian_to_saka",
"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.
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
The algorithm is pure arithmetic with a Julian Day Number offset walk—no network, no random seed, and no reliance on the host clock—so the free browser path and the paid API path always agree byte for byte on the same input.
Input contract, response fields, and validation behaviour
POST a JSON body with one required string field named date. The parser rejects missing values, non-strings, wrong separators, and wrong lengths with invalid_input and a clear English message that names the date field. On success the body echoes the normalised gregorian ISO string, saka_year as an integer era year, saka_month from one to twelve, saka_month_name as the English month label, saka_day as the day of that month, saka_date as a human display string such as twenty-four Shravana eighteen sixty-nine SE, is_saka_leap_year as a boolean true when Chaitra has thirty-one days, and day_of_saka_year as the one-based ordinal from New Year. Pair the response with your own UI labels; the API does not emit Devanagari glyphs or regional month aliases beyond the English civil names.
Where a Gregorian to Saka converter earns its keep
Developers shipping India-facing dashboards can call this parse-tier endpoint at the published $0.002 base price per successful item and skip model tokens entirely.
Technical questions
How do I convert a Gregorian date to the Indian Saka calendar?
Send JSON with date as YYYY-MM-DD. The API returns saka_year, saka_month, saka_month_name, saka_day, saka_date, is_saka_leap_year, and day_of_saka_year using official civil rules.
What does the Gregorian to Saka converter cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.