Each option sets one field of the request the Fetch Standard builds.
mode decides what a cross-origin request may do and what comes back. fetch() defaults to 'cors': a cross-origin response is readable only if the server opts in with CORS headers, otherwise the promise rejects with a TypeError. 'same-origin' rejects any cross-origin URL. 'no-cors' sends the request anyway, but only with GET, HEAD or POST (a PUT throws) and safelisted headers (others are silently dropped). You get an opaque response: type "opaque", status 0, ok false, no headers, an empty body. Script can't read it, only hand it on, for example to a service worker's cache. Which server headers make CORS succeed is CORS policy, not this option.
credentials decides when cookies, HTTP auth and client certificates go along. 'same-origin', the default, sends them only to your own origin. 'include' sends them cross-origin too, and the response is then usable only if the server explicitly allows credentials. 'omit' never sends them and ignores any Set-Cookie that comes back.
cache picks how this request uses the browser's HTTP cache:
'default': follow the response's caching headers.'no-store': skip the cache both ways.'reload': go to the network, then store the result.'no-cache': always revalidate; a 304 serves the cached body.'force-cache': use any cached copy, even stale.'only-if-cached': never touch the network; requiresmode: 'same-origin'.
This is the HTTP cache only, not the Cache API a service worker manages.
redirect: 'follow' (default), 'error' (a redirect becomes a network error) or 'manual' (an "opaqueredirect" response with status 0). referrerPolicy and referrer shape the Referer header; the default policy, strict-origin-when-cross-origin, sends only your origin to other origins.