Both are Storage objects with the same synchronous, string-only API: getItem(), setItem(), removeItem(), clear(), key(), length. They differ in scope.
localStorage belongs to the origin (scheme, host and port). Every tab and same-origin iframe shares one map, and it stays until script or the user clears it. localhost:8061 and localhost:8062 don't see each other's.
sessionStorage belongs to the origin and one tab (a top-level traversable, in spec terms). It survives reloads and navigation within the tab, including leaving the site and coming back, and same-origin iframes in the tab share it. A second tab on the same URL starts empty. It's deleted when the tab closes.
window.open() copies the opener's session storage into the new tab: a snapshot, after which the two drift apart. With noopener, which <a target="_blank"> implies, nothing is copied.
The storage event fires on every other same-origin Window that shares the changed storage, never on the one that made the change. It carries key, oldValue, newValue, url and storageArea; clear() sends key: null. Setting a key to the value it already has fires nothing. For localStorage the event reaches other tabs; for sessionStorage only same-origin iframes in the same tab, since other tabs have their own copy.
That makes the event a cheap way to sync small state such as a logout or a theme change across tabs. BroadcastChannel is the general tool for messages that aren't stored.
The Storage Standard gives each 5 MiB per origin. Chrome 156 and Firefox 159 both threw QuotaExceededError once keys plus values passed 5,242,880 UTF-16 code units.