# Cookie, JSON, and Base64: the difference

> A cookie carries browser state, JSON structures data, and Base64 encodes bytes. None of these labels alone defines access rights or lifetime.

## Cookie

A browser sends cookies back to the site that set them so the site can recognize a session and preferences. A session cookie may represent an authenticated login, so leaking it can expose the session.

## JSON

JSON stores objects, lists, strings, and numbers in a readable text structure. A .json file may hold harmless settings or sensitive tokens and cookies; its safety depends on the content.

## Base64

Base64 turns binary data into text. It helps transport data but does not hide it: a compatible decoder restores the original bytes.

## Safe handling

Inspect the file locally, never publish it, and never upload it to an unknown converter. Use the format only with an official client or software you deliberately trust when the product page names that format.

## Related

- [Account data formats: login, password, 2FA, token, cookie, and JSON](https://getproaccs.com/en/docs/account-data-formats)
- [Token, refresh token, and OAuth 2.0 explained](https://getproaccs.com/en/docs/tokens-and-oauth)
- [Safe first inspection of a digital account](https://getproaccs.com/en/docs/first-access-security)

## Sources

- [MDN: HTTP cookies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Cookies)
- [RFC 8259: JSON](https://www.rfc-editor.org/rfc/rfc8259)
- [RFC 4648: Base64](https://www.rfc-editor.org/rfc/rfc4648)

Canonical: https://getproaccs.com/en/docs/cookies-json-and-base64
Updated: 2026-10-11