A website cookie is a small piece of data your browser stores and can send back to the site on later requests. It can help a website recognize a signed-in session or remember a setting. A cookie is not a copy of an entire webpage.
A small note, not your whole account
MDN’s cookie guide describes a common login pattern: the browser stores a session identifier, then sends it with later requests so the server can recognize the session. The identifier connects the visit to information held elsewhere; it need not contain your password or every detail of your account.
Cookies can also support personalization and tracking. The word describes a mechanism, not a single purpose. A saved language choice and an advertising identifier can both use that mechanism while doing very different jobs.
Why clearing them changes a website
Google’s cache and cookies guidance explains that deleting this information can remove site settings and require another sign-in. Clearing cached images and deleting cookies are different actions, even when a browser places them in the same dialog.
Think about two annoyances: an old logo keeps appearing, or a website keeps remembering the wrong account. Those are different clues. Our practical suggestion is to identify the symptom first, then read the deletion options instead of selecting every checkbox automatically.
Read the purpose before choosing
When a site presents cookie choices, look for descriptions of what each category does. Ask: does this support the feature I am using, remember a preference, or measure activity? A button’s size or color tells you nothing about the answer.
For a simple exercise, note one site preference you would care about losing before changing any browser settings. That makes the tradeoff concrete. If you are troubleshooting, save unfinished work first and avoid treating a broad reset as the first step.
Continue with what your browser cache saves or what Incognito mode does.
