What are your real options to sync Google Calendar with Outlook?
Nothing built into Google or Microsoft writes an event back the other way, so to sync Google Calendar with Outlook reliably you always need a third tool — the only question is which kind. There are three routes. The first is a subscribed feed inside Outlook: paste in the other calendar's link and Outlook reads it on its own refresh schedule, one-way and view-only. The second is a desktop bridge, the best-known being Outlook Google Calendar Sync (OGCS), a Windows program that runs on your own PC and pushes changes between an Outlook and a Google account. The third is a hosted sync service, such as Keeper.sh, where the syncing runs on a server you never have to touch.
Which route fits comes down to one sorting question: do you only need to glance at the other calendar while you plan, or do you need events to show up as real, editable entries that stay correct in both places when something moves or gets cancelled? A feed answers the first case, and it never writes anything back. Only a tool that actually writes events through each provider's calendar — a bridge or a hosted service — answers the second.
Between those two tool routes, what decides it is where the sync runs — on your own machine, or on a server that keeps working when your computer is off, asleep, or closed.
Why is the Outlook route read-only and out of date?
The built-in Outlook route is a subscription: Outlook re-reads the feed on its own timer and has no way to send an edit made in Outlook back to Google, so it can never be two-way. In new Outlook and Outlook on the web, the click path is Add calendar > Subscribe from web, where you paste the Google secret iCal URL and select Import. In classic Outlook, it's File > Open & Export > Import/Export > Import an iCalendar (.ics) or vCalendar file (.vcs) > Next, and Microsoft's own documentation says the imported calendar "is a static snapshot; it does not self-update" — it is never re-read at all, so updating it means repeating the import by hand.
Even the subscribed version is slow. Microsoft publishes the refresh cadence for a subscribed feed: approximately every 3 hours for Outlook.com personal accounts, approximately every 6 hours for work or school accounts on Outlook on the web, and "can take more than 24 hours." Google's own Calendar Help pages give no equivalent figure for a URL-added calendar, so there's no official number for how long an edit takes to reach that feed.
What does two-way sync between Google Calendar and Outlook actually require?
Mechanically, two way sync google calendar outlook requires two separate one-directional connections running at once: one set from Google's calendar page pointed at Outlook, and a second set from Outlook's calendar page pointed back at Google, each configured on its own. That rests on a distinction worth defining once, here: a subscription only refreshes a view on the recipient app's own schedule, while a sync writes real events into the destination calendar itself — nothing gets copied unless something is actively putting it there. Once both directions are set up, every event exists twice: the original, and a second, separately-editable copy sitting in a real calendar on the other side, not a link back to the source.
What separates a sync tool worth using from one that just piles up clutter is whether it corrects those copies in place afterward, not just on the first pass. Move the original and the copy should move with it. Shorten it, retitle it, or delete it, and the copy should update or disappear rather than sitting there as a stale duplicate. That correction happens because the tool keeps a mapping between the two copies that outlives the event itself, so even a deletion at the source still reaches the other calendar on a later pass instead of leaving an orphaned entry behind.
Is Outlook Google Calendar Sync (OGCS) worth using?
Outlook Google Calendar Sync (OGCS) is free, open source, and genuinely feature-packed: it can sync Outlook to Google, Google to Outlook, or both directions at once, set per profile, which is exactly the tool most people find when they search sync outlook calendar with google calendar. It's a Windows desktop app, installer or portable, needing only .NET Framework 4.5, and it covers Outlook and Google exclusively — no iCloud, no Fastmail, no self-hosted calendar server. Being open source isn't a mark against it here; Keeper.sh ships under the same AGPL-3.0 licence.
The catch is where it runs. OGCS's own FAQ concedes it would be nice if the program didn't need "installing on a PC that is powered on for it to sync," and its maintainer explains why there's no hosted version: building one would demand either technical setup work from the user or hosting costs the maintainer would have to absorb. So the sync only happens while your Windows machine is on. Its automatic interval bottoms out at 15 minutes, or 120 minutes once Push Sync is turned on, though Outlook-side push detects a change within 2 minutes.
In practice that means: laptop shut, or you're checking your calendar from your phone, and nothing syncs until that PC wakes back up. For anyone who needs both calendars current without babysitting a desktop, that's the deciding constraint OGCS can't get around.
How do you keep both calendars in step without leaving a PC on?
Keeper.sh runs the sync server-side: nothing installs on your machine, nothing of yours has to stay awake, and there's no app to keep open on a phone — the syncing runs on Keeper.sh's own servers whether your laptop is on, closed, or asleep. If you want to sync Google Calendar with Outlook and have it keep working while the laptop is shut, that's the deployment difference that decides it.
Setup takes two passes, one per direction. Connect both your Google and Outlook accounts, then open the source calendar's page and, under Send Events to Calendars, tick the calendar that should receive its events. For two way sync google calendar outlook, repeat from the other calendar's page, ticking back the other way — each direction is its own connection with its own settings.
Sources are read every minute on every plan. On Pro, Google and Outlook notify Keeper.sh the moment something changes, landing the copy within seconds; on Free, copied events go out every 30 minutes instead.
Worth knowing before you connect anything: copies are private by default. A copied event is titled after the source calendar, not the real event name, and its description and location stay hidden unless you turn each on — set per calendar, so you choose what crosses over.
Free covers 2 accounts and 3 connections — a two-way pair between Google and Outlook already uses two of those three. Pro is $5 a month or $42 a year, for unlimited accounts and connections plus the seconds-level cadence. Keeper.sh is AGPL-3.0, so self-hosting gets every Pro feature at the cost of running the server yourself.
Which option should you actually pick?
Pick the subscribed feed only if you want to look at the other calendar and nothing more. It runs inside Outlook with nothing else to install, and it never writes an edit back.
Pick OGCS if you are on a Windows desktop that stays powered on around the clock, only need Outlook and Google, and want zero cost — its open-source engine and 15-minute floor cover exactly that case, and Keeper.sh's Pro tier buys nothing you'd use.
Pick Keeper.sh for everything else, because the syncing runs on Keeper.sh's own servers rather than on a machine of yours. A laptop that sleeps or gets shut for the night stops nothing, and checking from a phone works the same way. OGCS can do neither: it syncs only while that specific Windows PC stays on. On Pro, Google and Outlook notify Keeper.sh directly, so a change lands within seconds. And the moment iCloud, Fastmail or a generic CalDAV server joins the mix, OGCS is out — it speaks only Outlook and Google, where Keeper.sh treats all five as first-class.
What goes wrong after a two-way sync is running?
Once a connection is live, the maintenance left is almost entirely about access, not accuracy. Google or Outlook can revoke access after a password change, a withdrawn app-specific password, or an administrator policy, and Keeper.sh flags the account as needing reauthentication rather than failing silently — sign back in and the connection picks up where it left off. That flag is raised per account, not per connection, so in a two way sync google calendar outlook setup one side can be revoked and flagged while the other keeps polling; only signing back in clears it, since a source poll can't clear a demand raised by a lost destination grant.
Undoing a setup is deliberate rather than manual. Untick a calendar under Send Events to Calendars and Keeper.sh stops maintaining the copies it made there, and schedules the cleanup straight away rather than waiting for the next run. Narrowing a sync window works the same way: events now outside the range get removed, not just excluded going forward. Neither touches events you created yourself — cleanup only ever reaches copies Keeper.sh made.
One asymmetry worth remembering: a calendar added from a shareable link is a subscription, not a connection — it can send events out but never receive them back, since nothing writes to it through a provider calendar.