Skip to content
Conflict safety

Stop silent overwrites and accidental deletes in calendar sync.

Needs choice

How Kelbra does it

Kelbra detects the conflict instead of guessing. When the same event has changed on two sides since the last sync, that event pauses and shows both versions side by side until you pick which one wins.

Deletes, too

Deletes get the same safety net. Every event is backed up before it's removed from a synced calendar, so an accidental delete, whether yours or a sync mistake, can be recovered.

undefined

Setting this up

Ⅰ.

Connect the calendars you want to keep in sync.

Ⅱ.

If a conflict is ever detected, a banner appears on your dashboard and the affected event is frozen (not synced further) until you resolve it.

Ⅲ.

Open the Conflicts page, review both versions of the event, and choose which one should win. The other side updates to match.

Ⅳ.

Check History any time you want to see exactly what changed, when, and which calendar it came from.

Ⅴ.

If something was deleted that shouldn't have been, recover it from History.

Questions

What actually happens if I edit the same event on two calendars at once?

Kelbra detects that both sides changed since the last sync and freezes that one event. It stops syncing further until you review both versions and choose which one wins. Nothing is silently overwritten.

Can I get back an event I accidentally deleted?

Yes. Every event is backed up before it's removed from a synced calendar, so you can recover it from History instead of losing it for good.

Does conflict review slow down the rest of my sync?

No. Only the specific event in conflict is frozen. Every other event keeps syncing normally while you resolve it.

Keep reading

iCloud ↔ Google

Sync iCloud with Google, actually two-way

Outlook ↔ Google

Sync Outlook and Google without sharing details

CalDAV ↔ Google

Sync Fastmail or Nextcloud with Google

Stop copying events by hand.

Connect your first calendar in about a minute.

Get started