<commit_before>---
title: "Using cookies"
order: 28
page_id: "cookies"
search_keyword: "pm.cookies.jar, cookies.jar"
contextual_links:
  - type: section
    name: "Prerequisites"
  - type: link
    name: "Setting up Postman"
    url: "/docs/getting-started/settings/"
  - type: section
    name: "Additional Resources"
  - type: subtitle
    name: "Videos"
  - type: link
    name: "Syncing Cookies for Authentication | Postman Level Up"
    url: "https://www.youtube.com/watch?v=jfgFNw5SoUg"
  - type: subtitle
    name: "Related Blog Posts"
  - type: link
    name: "Using the Interceptor to read and write cookies"
    url: "https://blog.postman.com/using-the-interceptor-to-read-and-write-cookies/"

warning: false

---

Postman provides a **Manage Cookies** modal that lets you edit cookies that are associated with each domain. If you want to capture cookies using Postman Interceptor, refer to [Syncing cookies](/docs/sending-requests/capturing-request-data/interceptor/#syncing-cookies).

> You can disable the cookie jar in the __Settings__ tab for a request at any time to toggle off sending cookies.

## What are cookies?

A computer _cookie_ is more formally known as an HTTP cookie, a web cookie, an Internet cookie or a browser cookie. The name is a shorter version of “magic cookie,” which is a term for a packet of data that a computer receives and then sends back without changing or altering it.

## What information are stored along with a cookie?

A cookie typically contains two bits of data: a unique ID for each user, and a site name. Cookies enable websites to retrieve this information when you revisit them, so that they can remember you and your preferences and tailor page content for you based on this information.

## Why would someone want to use cookies?

As a necessary part of web browsing, HTTP cookies help web developers give you more personal, convenient website visits. Cookies let websites remember you, your website logins, your shopping cart data, and more.

## How is it useful?

Websites use HTTP cookies to streamline your web experiences. Without cookies, you’d have to log in again after you leave a site or rebuild your shopping cart if you accidentally closed a web page. This makes cookies an important a part of the internet experience.

## Getting to the cookie manager

To open the **Manage Cookies** modal, click the **Cookies** link under the **Send** button.

[![cookies link](https://assets.postman.com/postman-docs/58524551.png)](https://assets.postman.com/postman-docs/58524551.png)

This opens the **MANAGE COOKIES** modal, and displays a list of domains and the cookies associated with them.

[![manage cookies modal](https://assets.postman.com/postman-docs/WS-manage-cookies-1.png)](https://assets.postman.com/postman-docs/WS-manage-cookies-1.png)

## Create a cookie

To add a new cookie for the domain, click **Add Cookie**. A pre-generated cookie string compliant with [HTTP State Management standards](https://tools.ietf.org/html/rfc6265#section-4.1) will be created.

```js
<cookieName>=<cookieValue>; path=/; domain=.domain.com; HttpOnly; Secure; Expires=Tue, 19 Jan 2038 03:14:07 GMT;
```

Postman supports the following attributes:

* **cookieName**, **cookieValue**: The name of the cookie and the value stored in it.
* **Domain**: The domain Postman will send the cookie to.
* **Path**: The URL path that the cookie is restricted to. If the path is `/`, the cookie will be sent to all requests in the specified domain.
* **HttpOnly**: If present, the cookie won't be accessible to the client-side scripts run on the page (for example, with `document.cookie` in JavaScript). The cookie will only be added to the cookie header in requests that are made. This field does not have an effect on Postman's behavior.
* **Secure**: If present, the cookie is only sent when the URL begins with `https://`, and won't be sent over an insecure connection.<commit_msg>[MARKENG-430] Update resolved url in src/pages/docs/sending-requests/cookies.md<commit_after>---
title: "Using cookies"
order: 28
page_id: "cookies"
search_keyword: "pm.cookies.jar, cookies.jar"
contextual_links:
  - type: section
    name: "Prerequisites"
  - type: link
    name: "Setting up Postman"
    url: "/docs/getting-started/settings/"
  - type: section
    name: "Additional Resources"
  - type: subtitle
    name: "Videos"
  - type: link
    name: "Syncing Cookies for Authentication | Postman Level Up"
    url: "https://www.youtube.com/watch?v=jfgFNw5SoUg"
  - type: subtitle
    name: "Related Blog Posts"
  - type: link
    name: "Using the Interceptor to read and write cookies"
    url: "https://blog.postman.com/using-the-interceptor-to-read-and-write-cookies/"

warning: false

---

Postman provides a **Manage Cookies** modal that lets you edit cookies that are associated with each domain. If you want to capture cookies using Postman Interceptor, refer to [Syncing cookies](/docs/sending-requests/capturing-request-data/interceptor/#syncing-cookies).

> You can disable the cookie jar in the __Settings__ tab for a request at any time to toggle off sending cookies.

## What are cookies?

A computer _cookie_ is more formally known as an HTTP cookie, a web cookie, an Internet cookie or a browser cookie. The name is a shorter version of “magic cookie,” which is a term for a packet of data that a computer receives and then sends back without changing or altering it.

## What information are stored along with a cookie?

A cookie typically contains two bits of data: a unique ID for each user, and a site name. Cookies enable websites to retrieve this information when you revisit them, so that they can remember you and your preferences and tailor page content for you based on this information.

## Why would someone want to use cookies?

As a necessary part of web browsing, HTTP cookies help web developers give you more personal, convenient website visits. Cookies let websites remember you, your website logins, your shopping cart data, and more.

## How is it useful?

Websites use HTTP cookies to streamline your web experiences. Without cookies, you’d have to log in again after you leave a site or rebuild your shopping cart if you accidentally closed a web page. This makes cookies an important a part of the internet experience.

## Getting to the cookie manager

To open the **Manage Cookies** modal, click the **Cookies** link under the **Send** button.

[![cookies link](https://assets.postman.com/postman-docs/58524551.png)](https://assets.postman.com/postman-docs/58524551.png)

This opens the **MANAGE COOKIES** modal, and displays a list of domains and the cookies associated with them.

[![manage cookies modal](https://assets.postman.com/postman-docs/WS-manage-cookies-1.png)](https://assets.postman.com/postman-docs/WS-manage-cookies-1.png)

## Create a cookie

To add a new cookie for the domain, click **Add Cookie**. A pre-generated cookie string compliant with [HTTP State Management standards](https://datatracker.ietf.org/doc/html/rfc6265#section-4.1) will be created.

```js
<cookieName>=<cookieValue>; path=/; domain=.domain.com; HttpOnly; Secure; Expires=Tue, 19 Jan 2038 03:14:07 GMT;
```

Postman supports the following attributes:

* **cookieName**, **cookieValue**: The name of the cookie and the value stored in it.
* **Domain**: The domain Postman will send the cookie to.
* **Path**: The URL path that the cookie is restricted to. If the path is `/`, the cookie will be sent to all requests in the specified domain.
* **HttpOnly**: If present, the cookie won't be accessible to the client-side scripts run on the page (for example, with `document.cookie` in JavaScript). The cookie will only be added to the cookie header in requests that are made. This field does not have an effect on Postman's behavior.
* **Secure**: If present, the cookie is only sent when the URL begins with `https://`, and won't be sent over an insecure connection.
{'fraction_non_alphanumeric': 0.0905422446406053, 'fraction_numerical': 0.01021437578814628, 'mean_word_length': 4.273271276595745, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 9, 'https://': 16, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '813183', 'n_tokens_mistral': 2271, 'n_tokens_neox': 2147, 'n_words': 1044}