Cookie Converter Online — Cookie Studio
Convert cookies between JSON, Netscape, Base64, and Cookie String. Bulk-process TXT/CSV, inspect errors, and export separate files as ZIP — locally in your browser.
Use this section to convert one cookie set or multiple lines. Enter the source, choose an output format, then find the result in section 2.
Step-by-step: convert your cookies
This section converts cookie data; it does not log in to accounts or check whether sessions are still valid.
- Choose the input mode. “Single document” is for one set (for example
session=demo123; theme=light). “Multiple cookie sets” expects one set per line. “Mixed records” is for lines with several columns, where one column contains cookies. - Paste or upload the source. Paste text into “Paste cookies”, or select a
.txt,.jsonor.cookiesfile. Use “Example” to learn without real session data. - Pick the output format. JSON Cookies preserves known attributes; Base64(JSON) encodes that JSON; Cookie String contains
name=valueonly; Netscape uses a seven-column text format. - Set a domain only when needed. The optional domain is assigned only to cookies that have no source domain. Netscape export requires a domain. Existing domains are not silently replaced.
- Check mixed-record columns. For “Mixed records”, click “Analyze fields” and confirm the delimiter and cookie column. If auto-detection is ambiguous, select both manually.
- Review possible attribute loss. Cookie String and Netscape may discard attributes. Read the warning and tick the consent box only if you accept that limitation.
- Convert. Click “Detect and convert”. The converted data, set count and errors will appear in section 2.
If a domain is missing from the source cookies, it will not be invented. Netscape export requires a domain; you can enter one above.
The output of section 1 appears here automatically. You do not need to type into the result field.
Step-by-step: understand and save the result
Review the converted data and choose the appropriate download.
- Run section 1 first. The output is populated after “Detect and convert”. If it is empty, return to the input section.
- Review the counters. “Cookies” is the number of parsed cookie pairs, “Sets” counts recognised sets, and “Errors” counts problematic records. Read the status message.
- Copy or download. “Copy result” copies the visible output; “Download result” saves it in the selected format.
- For mixed records, keep other fields. Choose “Download TXT (preserve fields)” to keep the original record layout with the cookie column converted. Note: other fields, including any source credentials, stay in the TXT file.
- Investigate errors. Use “Download error report CSV” when enabled to locate record numbers and error categories.
- After changing the input. Run conversion again before downloading. Avoid using a result created from an earlier input.
Bulk mode retains original row numbers. For mixed records, download TXT to preserve additional fields. Never publish exported files: they may contain secrets.
Supported: Cookie String / HTTP Cookie, Netscape cookies.txt, JSON arrays, some JSON wrappers, Base64(JSON), and mixed rows with |, TAB, :, ;, comma, and custom delimiters. Different JSON schemas may look similar. Verify the result before importing.
Convert a cookie column across many TXT/CSV rows while preserving the other columns.
Step-by-step: bulk TXT/CSV conversion
Use this mode for a single output file with the original record layout.
- Prepare a TXT or CSV. Use clear columns, for example
user@example.invalid|demo-pass|session=abc(synthetic data). In CSV, fields containing delimiters, quotes or line breaks must use proper CSV quoting. - Choose a file. Select “TXT / CSV file”. The maximum file size for this mode is 15 MB.
- Choose cookie output format. JSON, Base64(JSON), or Cookie String are available. Netscape creates multiple lines per cookie set; use section 5 for separate Netscape files.
- Analyze the file first. Leave “Automatic” selected and click “Analyze file”. Inspect the detected delimiter and cookie column. If either is wrong, choose the settings manually.
- Review the header option. Tick “Skip header” only if the first row contains column headings rather than cookie data. Column numbers start at 1, so the third field is column 3.
- Process and check counts. Click “Process file”. Review total, successful and failed records. Invalid records are left unchanged rather than silently repaired.
- Download the output and audit. “Download result” saves the converted TXT/CSV, “Download JSON report” gives summary statistics, and “Download errors CSV” lists problem record numbers and reasons without raw secret values.
For large line-based files or CSV with quotes and embedded line breaks. Data is processed only in your browser; the original file is not changed.
The sample contains synthetic data only. After uploading, click “Analyze file” and check the delimiter, cookie column (numbering starts at 1), and header. Other columns are preserved; invalid records remain unchanged.
Netscape requires a separate file for each cookie set. Use section 5, “Bulk ZIP export”; Netscape cannot be embedded in mixed TXT/CSV rows.
If you change the output format, process the file again. Cookie String and Netscape may discard additional attributes.
Warning: unescaped delimiters inside cookie values can make field boundaries ambiguous. Use CSV quoting or a safe delimiter. Invalid records are left unchanged. Download is available only after round-trip verification.
Prepare one cookie set for any of the same 24 programs listed in section 5. For many sets, use section 5. When a vendor-specific import schema is unverified, standard JSON is generated and clearly labelled as unverified.
Step-by-step: JSON profile for one cookie set
This only checks structure and prepares the file. It does not sign in, call an API, or confirm that a target application will accept the exported file.
- Enter one set in section 1. Return to “Input data”, select “Single document” and paste the cookie set. Alternatively, click “Example cookies” here to automatically add synthetic data to section 1.
- Select the target schema. Choose from 21 antidetect browsers and 3 advertising automation tools. Standard JSON, Playwright addCookies(), and experimental Dolphin{anty} Remote API cookies are additional options. Unverified vendor schemas use universal JSON, not a purported vendor-specific importer.
- Read validation requirements. The “Format and limitations” field shows the evidence level and restrictions. Some formats require a domain or URL. Open the available documentation link if necessary.
- Review any potential data loss. Only allow unsupported attributes to be excluded after reading the warnings. Do not assume a profile preserves every field.
- Validate and prepare. Click “Validate structure and prepare JSON”. Review the status, JSON output and audit without exposing cookie values in diagnostic messages.
- Download the JSON. If validation passes, click “Download profile JSON”, then follow the vendor’s own import instructions.
Prepare one JSON cookie set locally. The file structure is checked; actual import into third-party applications is not verified. This does not log in, import into a browser, or call an API. First paste one set in section 1. Values are hidden in diagnostics but included in the downloaded file.
Sections 4 and 5 list the same 24 programs. A documented JSON format is not proof of successful import. Universal JSON for other programs is intended for manual verification, not a vendor-specific schema. FBTOOL exports Facebook cookies, not a full account template; Playwright and Dolphin API have separate specialized formats.
One valid cookie set becomes one separate file inside the downloaded ZIP archive.
Step-by-step: export multiple cookie files to ZIP
Choose from 21 antidetect browsers and 3 ad automation tools, then generate files and an audit report.
- Upload a source file. Select a TXT/CSV up to 15 MB using “Source TXT/CSV”. “Download sample CSV” gives you a synthetic file for trying the workflow.
- Choose the target program. Select from the 21 browsers or 3 ad automation tools. Read “Selected profile format” and the compatibility status. Vendor documentation is linked when available.
- Choose the file format. Select JSON, Netscape cookies.txt, Base64(JSON), or Cookie String. Some targets lock the format to JSON, such as FBTOOL. A program may not support every generic export.
- Check delimiter, column and header. Use auto-detection or set the delimiter manually. Cookie column numbering starts at 1. Tick “Skip header” only when a header was detected.
- Set optional domain and consents carefully. A user-provided domain applies only to cookies that have none. Acknowledge attribute loss only when acceptable. The FBTOOL filter removes cookies from other domains permanently from the export; do not enable it casually.
- Analyze before processing. Click “Analyze” and inspect the structure-only preview: column counts, cookie column, header and possible ambiguities. Cookie values are not displayed.
- Prepare the ZIP. Click “Prepare ZIP” and wait for progress to finish. You may cancel a running operation. Review success/failure counts and quality warnings.
- Download files and report. Use “Download ZIP” and optionally “Download JSON report”. The ZIP includes one cookie file per valid set,
manifest.csv,report.jsonandREADME.txt. - Unzip before importing. Extract the archive and use the files according to the selected program’s requirements. The ZIP itself is generally not a direct cookie-import file.
Each successfully processed cookie set is saved as a separate file inside a ZIP. Choose from 21 antidetect browsers and 3 ad automation tools. The selected profile does not guarantee successful importing. Unzip the archive before importing. Processing runs locally in your browser. This release includes safe structure previews, progress, cancellation, a separate JSON report and error categories without account data. Cookie values are not included in reports.
If provided, it is assigned only to cookies without a domain. It is not a recovered original attribute.
| Row # | Columns | Cookie field | Record type |
|---|
Only row numbers and broad error categories are displayed. The full list is in report.json.
The archive contains cookies_000001.*, manifest.csv, report.json with attribute diagnostics, and README.txt. Unzip before importing. Passwords and original lines are not included in the ZIP; they remain in your source TXT/CSV and can be preserved through section 3 exports. No automatic sign-in or data transfer to the listed services.
How to use CrazyFB Cookie Studio
- For a single cookie set, paste cookies in section 1. For a file with multiple sets, use section 3 or 5.
- Choose the desired output format. For bulk processing, upload a file in section 3 or 5.
- After file analysis, verify the delimiter, cookie column number, and whether to skip the header.
- Download your result. Unzip the ZIP archive first, then import its individual files and check the target program requirements.
Frequently asked questions
Which cookie formats are supported?
JSON Cookies, Base64(JSON), Cookie String, and Netscape cookies.txt. Some formats cannot preserve every original cookie attribute; the tool warns about this.
Can I process many records at once?
Yes. Bulk tools accept TXT/CSV, and ZIP export creates one file per successfully parsed cookie set. Invalid records are listed in the report.
Does it support antidetect browsers and ad automation tools?
The target list includes 21 antidetect browsers and 3 ad automation tools: FBTOOL, Dolphin Cloud, and Nooklz. Some have documented formats; others use a generic export. Actual import into a specific application is not guaranteed until tested.
Does CrazyFB Cookie Studio store my cookies or uploaded files?
No. The CrazyFB Cookie Studio converter itself does not send the cookies you enter or TXT/CSV files you select to CrazyFB.shop servers, and it does not store them in a database. Analysis, conversion, and file generation take place locally in your browser. Your original file is not modified, and generated results are downloaded directly to your device. While the page is open, input and generated results may remain in the tab’s memory; clear the fields or close the tab when you finish. Session cookies can provide access to accounts, so keep exported files private. This describes the converter itself, not every third-party script that may be present on the website.
Why might cookies fail to import?
Possible causes include incorrect domains, expiration, unsupported attributes, incompatible file format, or importer restrictions. Diagnostics flag issues without silently modifying the original cookies.