react-big-calendar: A React Event Calendar With a Localizer You Must Choose
gcal/outlook like calendar component
At a glance
- What is it?
- react-big-calendar is a gcal/outlook-like events calendar component for React. It is MIT licensed, needs a date library wired in through a localizer, and the container element must be given a height or nothing shows up.
- Who is it for?
- Adopt react-big-calendar when you need a month or week grid with events inside an existing React app and you already have a date library you are happy with. Do not adopt it as a scheduler: there is no resource or room booking model in the README, and the drag and drop support is an addon with its own stylesheet rather than a core feature.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 168 days ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- bigcalendar/react-big-calendar8,767 ★ · +11
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| bigcalendar/react-big-calendar | 8.8k | 8.8k |
11 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What react-big-calendar actually replaces
Most React teams that need a calendar end up writing one, and they usually write the same three things: a month grid, a week grid with overlapping timed events, and a list view for the current period. react-big-calendar ships those views as components. The README describes it as "an events calendar component built for React and designed for modern browsers (read: not IE)" and notes that it uses flexbox rather than the classic table-caption approach. That last detail matters more than it sounds. A table-based month grid is easy to lay out and hard to make responsive; a flexbox grid is the reverse. The project chose the responsive side.
The intended audience is a developer embedding a calendar into an application that already has its own data layer. The component does not fetch events, does not persist them, and does not own routing. You hand it an array, it draws it. That is the whole contract, and it is why the library stays small enough to read.
The project is explicit that it was inspired by Full Calendar, which is the honest framing. This is the React-native version of that idea, distributed as a component rather than as a framework you mount into a DOM node.
The localizer requirement and why it is not optional
The single most important design decision in react-big-calendar is that it does not format dates itself. The README states that regardless of your choice, you must choose a localizer. Four are provided: Moment.js, Globalize.js, date-fns and Day.js. Each one is a thin adapter that translates the library's internal date operations into whatever API your date library exposes.
This is a good trade. Bundling a date library into a calendar component forces a version on every consumer, and date libraries are exactly the kind of dependency teams already have opinions about. The cost is that the calendar cannot work until you wire one up, and the wiring is not uniform across the four. The Day.js localizer, for instance, extends Day.js with a specific set of plugins: IsBetween, IsLeapYear, IsSameOrAfter, IsSameOrBefore, LocaleData, LocalizedFormat, MinMax and UTC. The date-fns localizer takes a different shape again, accepting format, parse, startOfWeek, getDay and a locales object as a single configuration argument.
There is no documented default and no fallback. A calendar rendered without a localizer is a configuration error, not a degraded mode.
Installing react-big-calendar and rendering a first month view
The README gives the install command directly. Both package managers are supported.
yarn add react-big-calendaror
npm install --save react-big-calendarTwo things have to happen before anything appears on screen. First, import the compiled stylesheet. The README names the path explicitly: react-big-calendar/lib/css/react-big-calendar.css. Second, the container element must have a height. The README warns that without one, the calendar will not be visible.
The README's own Moment.js example is the shortest working configuration. It imports the Calendar component and the momentLocalizer, builds the localizer once outside the component, and passes events plus startAccessor and endAccessor.
import { Calendar, momentLocalizer } from 'react-big-calendar'
import moment from 'moment'
const localizer = momentLocalizer(moment)
const MyCalendar = (props) => (
<div>
<Calendar
localizer={localizer}
events={myEventsList}
startAccessor="start"
endAccessor="end"
style={{ height: 500 }}
/>
</div>
)Note that the height is set on the Calendar itself through style. That is the constraint from the previous paragraph, satisfied inline. The startAccessor and endAccessor props tell the component which fields on each event object hold the dates, so your event shape does not have to match the library's.
If you prefer date-fns, the localizer is constructed differently and takes the individual functions as arguments:
import { Calendar, dateFnsLocalizer } from 'react-big-calendar'
import format from 'date-fns/format'
import parse from 'date-fns/parse'
import startOfWeek from 'date-fns/startOfWeek'
import getDay from 'date-fns/getDay'
import enUS from 'date-fns/locale/en-US'
const locales = { 'en-US': enUS }
const localizer = dateFnsLocalizer({
format, parse, startOfWeek, getDay, locales,
})The README labels this example as date-fns v2, so the import paths above are the v2 paths. If your project is on a different major version, the function signatures are the thing to check first, not the calendar.
To run the project's own examples locally rather than building your own, the README gives a clone-and-storybook sequence:
git clone [email protected]:bigcalendar/react-big-calendar.git
cd react-big-calendar
yarn
yarn storybookThe README says Storybook then serves on localhost:9002.
Styling: compiled CSS or SASS variables
The default path is to import the compiled CSS and move on. Teams that need the calendar to match an existing design system get a second option: SASS sources ship with the package, and the README shows importing them directly.
@import 'react-big-calendar/lib/sass/styles';
@import 'react-big-calendar/lib/addons/dragAndDrop/styles'; // if using DnDThe SASS build exposes a variables file with color and sizing values you can override. The README adds a caution worth taking literally: changing or overriding styles can cause rendering issues, and each change should be tested carefully. That is a normal warning for a component whose layout depends on flexbox math, but it also tells you the project does not consider deep restyling a supported, guaranteed-stable surface.
If you are using the drag and drop addon, note that the second import above is separate. The addon has its own stylesheet and is not part of the base CSS.
Where react-big-calendar is the wrong tool
The component renders events. It does not schedule them. If your requirement is resource booking, room allocation, recurring event expansion with exception handling, or conflict detection across attendees, none of that appears in the README, and the library does not claim to do it. You would be building that layer yourself on top of a view component, which is a reasonable thing to do but should be a deliberate decision rather than an assumption.
Drag and drop is a second boundary. It is described as an addon with its own stylesheet import, not as core behaviour. Treat it as an extension with its own surface area.
The third limitation is the one the README states outright: the component targets modern browsers and explicitly excludes IE. If you have any requirement to support legacy browsers, this is not a library you can negotiate with, because the flexbox layout approach is the reason it exists.
Finally, the localizer coupling cuts both ways. Choosing a date library to satisfy react-big-calendar means that library is now in your bundle for the calendar's sake. If you have no other use for Moment.js, you are paying for it here.
react-big-calendar vs Full Calendar
The README says react-big-calendar was inspired by Full Calendar, and the comparison is the one people actually make. react-big-calendar is a React component that participates in your component tree and receives events as props.
That distinction decides the choice more often than any feature list. If your application is React and you want the calendar to re-render when your state changes, the component model is a better fit because there is no imperative bridge between your state and the calendar's internal state.
The second real difference is the localizer. react-big-calendar pushes that decision to you, which is either flexibility or an extra wiring step depending on how you feel about owning your date library.
Maintenance, licence and upgrade cost
The repository is not archived, and the last push to master was on 2026-06-01. The release history shows v1.20.0 on 2026-06-01, v1.19.6 on 2026-05-29, and v1.19.4 on 2025-06-16. The gap between v1.19.4 and the 2026 releases is roughly a year, so the cadence is not steady and you should not plan around frequent releases.
The versioning is standard semver on the 1.x line, which means minor releases can carry behaviour changes in a project this old. The practical upgrade cost is concentrated in two places: the localizer adapter, because it is coupled to your date library's API, and the CSS, because the SASS variables are documented as a surface where overrides can break rendering. A dependency bump that touches either one deserves a visual check of all the views you use, not just the default month view.
The licence is MIT, which is permissive and permits commercial use and modification. The package.json declares it and the LICENSE file is in the repository root. That is a statement about the licence terms, not legal advice; if your organisation has a dependency review process, the file to hand it is LICENSE.
Editorial conclusion
Adopt react-big-calendar when you need a month or week grid with events inside an existing React app and you already have a date library you are happy with. Do not adopt it as a scheduler: there is no resource or room booking model in the README, and the drag and drop support is an addon with its own stylesheet rather than a core feature. Before wiring it into a product, verify three things in your own checkout: that the localizer API matches the date library version you have pinned, that the container element you pass the calendar into has an explicit height, and that the CSS import resolves to lib/css/react-big-calendar.css in your bundler. The last push to master was on 2026-06-01, so treat v1.20.0 as the version you are evaluating rather than something that changes under you weekly.
Frequently asked questions
How do I install react-big-calendar?
Install it with yarn add react-big-calendar or npm install --save react-big-calendar, then import react-big-calendar/lib/css/react-big-calendar.css for the styles. The README also warns that the calendar's container element must have a height or the calendar will not be visible.
How do I use react-big-calendar in a React component?
You import the Calendar component and a localizer, build the localizer outside the component, and pass localizer, events, startAccessor and endAccessor as props. The README's example sets a height on the Calendar through the style prop so the grid has room to render.
What is react-big-calendar?
It is an events calendar component built for React and aimed at modern browsers, using flexbox instead of the classic table-caption layout. The README describes it as inspired by Full Calendar, and it is a calendar component you feed events into.
Is react-big-calendar free?
Yes. The repository declares the MIT licence and the LICENSE file sits in the repository root, so the package is published under a permissive open source licence.
How does react-big-calendar compare with Full Calendar?
The README states react-big-calendar was inspired by Full Calendar. react-big-calendar is a React component that takes events as props and requires you to choose a localizer for date formatting.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/bigcalendar-react-big-calendar)Star history chart for your README
[](https://hysenlabs.com/projects/bigcalendar-react-big-calendar)Was this useful?