Cookie Viewer & Editor
View, filter, copy, create, edit, and delete cookies
About Cookie Viewer & Editor
Cookies are small pieces of data that websites store in your browser to remember information about you. Our Cookie Viewer & Editor gives you complete control over these cookies, allowing you to view, create, edit, and delete them directly from your browser. Whether you're a developer debugging web applications or a privacy-conscious user managing your data, this tool provides everything you need.
What Are Browser Cookies?
Browser cookies are text files containing small amounts of data that websites send to your browser. They serve many purposes: keeping you logged in, remembering your preferences, tracking shopping carts, and personalizing your experience. Cookies can be session-based (deleted when you close your browser) or persistent (stored for a specified duration).
Key Features
- View All Cookies: See every cookie stored for the current domain in an easy-to-read format
- Filter by Name: Quickly find specific cookies using the search filter
- Copy Values: One-click copying of cookie values for testing or debugging
- Create New Cookies: Set custom cookies with specific names, values, paths, and expiration dates
- Edit Existing Cookies: Modify cookie values and attributes on the fly
- Delete Cookies: Remove individual cookies or clear all cookies at once
- Secure Flag Support: Set the Secure flag to ensure cookies are only sent over HTTPS
How to Use the Cookie Viewer
- The tool automatically loads all cookies for the current domain when you open the page
- Use the filter field to search for specific cookies by name
- Click "Copy" next to any cookie to copy its value to your clipboard
- Click "Edit" to populate the form with that cookie's current values for modification
- Click "Delete" to remove a specific cookie, or "Delete All" to clear all cookies
- To create a new cookie, fill in the form fields and click "Save Cookie"
Common Use Cases
Web Development & Testing: Developers use cookie viewers to debug authentication issues, test different user states, and verify that cookies are being set correctly. You can quickly create test cookies, modify session data, and clear cookies between tests without opening browser DevTools.
Privacy Management: Privacy-conscious users can see exactly what data websites are storing in their browser. This transparency helps you understand tracking mechanisms and delete unwanted cookies that may be following your browsing activity.
Troubleshooting Login Issues: Sometimes corrupted or expired cookies cause login problems. By viewing and deleting problematic cookies, you can often resolve authentication errors without clearing all your browser data.
Understanding Cookie Attributes
Name & Value: The cookie's identifier and the data it stores. Names should be unique within a domain.
Path: Specifies which URL paths can access the cookie. The default "/" means the cookie is available across the entire domain. Setting a specific path like "/admin" restricts the cookie to that section.
Domain: Determines which domains and subdomains can access the cookie. For security, you can only set cookies for the current domain or its subdomains.
Expiration: Controls how long the cookie persists. Session cookies (no expiration set) are deleted when you close your browser. Persistent cookies remain until their expiration date.
Secure Flag: When enabled, the cookie is only transmitted over HTTPS connections, protecting it from interception on insecure networks.
Security & Privacy
This tool operates entirely in your browser using JavaScript's document.cookie API. No cookie data is sent to any server or third party. However, note that HttpOnly cookies (set by servers with the HttpOnly flag) cannot be accessed or modified through JavaScript for security reasons. These cookies are invisible to this tool and can only be managed through browser settings or server-side code.
Frequently Asked Questions
HttpOnly cookies are not accessible to JavaScript and can't be viewed or modified from a page for security reasons. These cookies are set by the server with the HttpOnly flag to prevent client-side scripts from accessing sensitive data like session tokens.
No. Browsers restrict cookies to the current domain/scope for security. You can set subdomain cookies with proper domain attributes if allowed, but cross-domain cookie setting is blocked by the same-origin policy.
The Secure flag ensures that cookies are only sent over HTTPS connections, not HTTP. This prevents cookies from being transmitted in plain text over insecure connections, protecting sensitive data from interception.
Leave the 'Expires in days' field empty when creating a cookie. This creates a session cookie that will be deleted when the browser is closed. For a long-lasting cookie, set a very high number of days (e.g., 3650 for approximately 10 years).
The path attribute specifies which URL paths can access the cookie (default is /). The domain attribute specifies which domains and subdomains can access the cookie. For example, setting domain to .example.com allows both example.com and subdomain.example.com to access the cookie.