JSON整形
JSONを読みやすく整形します。
開発ツール
URLエンコード・デコード
URLの変換とパラメーター解析を行います。
URLエンコード・デコード
UtilBrix が提供詳しい方法と使用例は英語で提供しています。
Step-by-step instructions (English)
- Choose whole-URI encoding, component encoding, decoding, or query parsing.
- Paste the URL, individual parameter value, or query string that matches that mode.
- Run the conversion and inspect reserved characters before copying the result.
計算式と方法
URI encoding preserves structural characters such as slashes and colons. URI component encoding also escapes those characters, making it suitable for parameter values. Query parsing lists each key-value pair, preserving duplicate parameter keys.
使用例
The component hello world becomes hello%20world. Query name=Aman&page=2 produces two key-value pairs.
When this tool is useful
Prepare query parameter values, decode escaped URLs, or inspect repeated parameters in a request. Choosing the operation based on whether you have a whole URL or a single value avoids accidentally changing URL structure.
Common mistakes and limitations
- Encoding a complete URL as a component escapes separators such as slashes and colons.
- Encoding an already encoded value can turn percent signs into %25 and create unwanted double encoding.
Practical questions about this tool (English)
Which mode should I use for a parameter containing an ampersand?
Encode URI Component protects the ampersand as part of the value so it does not become a separator between parameters.
Why does a plus sign sometimes become a space?
Query-string parsing follows form-style query conventions, where plus commonly represents a space. Direct URI-component decoding follows a different operation; select the mode that matches your source.