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.