Parsing rulesPHP serialize string lengths are UTF-8 byte lengths, so parsing happens at the byte level — hand-edited strings with stale lengths fail with an exact position. Objects become JSON with a __class marker and convert back; R/r references are not supported.

PHP serialize

Load data

JSON

Converted output will appear here

Read WordPress / Laravel DB fields

PHP serialize to JSON

Two-way · auto byte-length recalculation · exact error position · local

🔒Processed locally in your browser — never uploaded or stored

No upload, no storage

JSON is processed in memory and never sent to a server.

Share via URL fragment

Share links encode data in the # anchor — never sent to a server.

Remember last edit

Optionally keep your last input locally; clear it with one click.

Why use PHP serialize to JSON

Read stored fields

WordPress options / meta and legacy Laravel serialize strings become readable JSON the moment you paste them.

No manual byte math

The worst part of hand-editing serialize data is recalculating s:N byte lengths; the reverse conversion recalculates them in UTF-8 automatically.

Two-way conversion

Convert to JSON to read and edit, then back to serialize to write straight into the database.

Exact error position

Length mismatches and truncated strings report the byte offset — not a vague parse error.

Local · no upload

Database payloads are often sensitive; converting entirely in your browser keeps them safe.