URL 인코더 / 디코더
URL을 인코딩하고 디코딩합니다
추천 다음 단계
관련 도구
사용 방법
텍스트 붙여넣기 또는 입력
입력 영역에 텍스트, 코드 또는 데이터를 입력하세요.
옵션 선택
적용할 변환이나 포맷을 선택하세요.
결과 복사
한 번의 클릭으로 출력을 클립보드에 복사하세요.
이 도구를 사용하는 이유
100% 무료
숨겨진 비용도, 프리미엄 등급도 없습니다 — 모든 기능이 무료입니다.
설치 불필요
브라우저에서 완전히 실행됩니다. 소프트웨어를 다운로드하거나 설치할 필요가 없습니다.
프라이빗 & 안전
데이터가 기기 밖으로 나가지 않습니다. 어떤 서버에도 업로드되지 않습니다.
모바일 지원
완전 반응형 — 스마트폰, 태블릿, 데스크톱에서 사용할 수 있습니다.
URL Encoding: Percent-Encoding for Safe Web Addresses
Key Takeaways
- URL encoding (percent-encoding) replaces unsafe characters with %XX hex values to ensure URLs are transmitted correctly.
- Spaces, ampersands, question marks, and non-ASCII characters all require encoding when used in URL parameters.
- All encoding and decoding is performed in your browser — no data is sent to any server.
URLs can only contain a limited set of ASCII characters. When you need to include spaces, special characters, or Unicode text in query parameters or path segments, URL encoding (also called percent-encoding) converts them into a universally safe format. Proper URL encoding prevents broken links, security vulnerabilities, and data corruption in web applications.
Improper URL encoding is among the OWASP Top 10 causes of web application injection vulnerabilities.
Security Impact
Key Concepts
Reserved vs. Unreserved Characters
RFC 3986 defines unreserved characters (A-Z, a-z, 0-9, -, _, ., ~) that need no encoding. Reserved characters (: / ? # [ ] @ ! $ & ' ( ) * + , ; =) have special meaning in URLs and must be encoded when used as data.
encodeURI vs. encodeURIComponent
encodeURI() encodes a full URI but preserves reserved characters. encodeURIComponent() encodes everything except unreserved characters, making it correct for encoding individual query parameter values.
Unicode and UTF-8 Encoding
Non-ASCII characters (Chinese, Arabic, emoji) are first converted to UTF-8 bytes, then each byte is percent-encoded. The character '日' becomes %E6%97%A5.
Double Encoding Pitfalls
Double encoding occurs when already-encoded values are encoded again (% becomes %25). This creates broken URLs and is a common source of bugs in URL construction.
Pro Tips
Always use encodeURIComponent() for query parameter values, never encodeURI() — the latter will not encode & and = characters.
Decode URLs before displaying them to users for readability, but always keep them encoded in HTTP requests.
Be careful with the '+' character — in query strings it represents a space (application/x-www-form-urlencoded), but in path segments it is literal.
Test URL encoding with international characters (CJK, Arabic, emoji) to ensure your application handles multibyte UTF-8 correctly.
All URL encoding and decoding is performed entirely in your browser. Your URLs and query parameters are never sent to any external server.