How many devices run the plugin with the same vault.

devices

Hours Obsidian is open and you are actively writing. The rest (24 − active) is idle polling at 30 s intervals.

20 h idle

How many times per day the idle debounce fires and triggers a sync on one device. ~5 per active hour is a typical estimate.

syncs / day

Average number of files uploaded or downloaded per sync event. Light: 2 · Moderate: 3 · Heavy: 5+

files

Total files in your vault. Affects LIST cost — R2 paginates at 1 000 objects, so a 5 000-file vault costs 5 LIST ops per sync walk.

files
Class A Write / List ops per month
— of 1M free tier
Class B Read / Head ops per month
— of 10M free tier
Operation breakdown
Source Class Total / month Per device
Sentinel poll (HEAD) B
Own syncs — LIST + PUT + sentinel PUT A
State-aware pulls — LIST (cross-device) A
Own syncs — ETag HEAD per upload B
State-aware pulls — file GET + sentinel GET B
Polling dominates Class B The 2 s active / 30 s idle sentinel HEAD rhythm accounts for ~94 % of all Class B ops. File transfers are a small fraction. Adjusting active hours has the largest impact on your B budget.
Large vaults amplify Class A R2 paginates LIST at 1 000 objects. A 10 000-file vault costs 10 LIST ops per sync walk — regardless of how many files actually changed. This is the dominant Class A cost for large vaults.
Absolute worst case (Heavy · 3 devices · 10 000 files) Class A ≈ 130K (13 % of 1M) · Class B ≈ 1.58M (15.8 % of 10M). Both well within the free tier with 85 %+ headroom.