Stable signalNo paid features detectedHigh-risk permissions
Set Character Encoding icon

Set Character Encoding

Provide right-click menu to manually set character encoding for web pages.

Users200KCurrent public install base
Rating4.0Store average score
Reviews290Public review volume
Manifest versionV3Extension platform version
7-day growth0Net users gained this week
7-day growth rate0%Relative weekly velocity
Preview

Set Character Encoding Media preview

2 assets
Trend

User growth trend

Review user movement across collected snapshots.

User Growth Over Time

200K200K200K200K200K2026年7月15日2026年7月18日2026年7月21日Latest: 200K
Rating trend

7-day rating trend

View collected rating snapshots from the latest 7-day window to assess rating stability.

7-day rating change

Start
4.02
Latest
4.02
7-day rating change
0.00
3.923.974.024.074.122026年7月15日2026年7月18日2026年7月21日Latest: 4.02
2026年7月15日2026年7月21日
Growth overview

Daily, weekly, and monthly growth

Compare 1-day, 7-day, and 30-day net growth and growth rate.

1-day growthFlat
00%
7-day growthFlat
00%
30-day growthFlat
00%
Technical snapshot

Version, languages, and crawl freshness

Review publication date, version, supported languages, and crawl timestamps.

Version1.0.1
ManifestV3
Size155KiB
Languages2English / 日本語
Published
Store updated
Last crawled
English日本語
Overview

Product summary

Review the store description, core capabilities, and common use cases.

Right-click at somewhere on web page to manually set character encoding. The selected character set will automatically apply to all pages on the same site. Select "Use page default" to cancel it. This extension modifies http response headers to override original character set, so when installing Chrome will say "it can read and change all your data on the websites you visit". Just let it go because that is exactly how it works.

Starting from V0.4, it supports changing encoding of local files, but you need check 'Allow access to file URLs' in extension manage page.

Starting from Chrome 72, old versions will stop working because new Chrome requires extensions to request for extra permission to modify response header. Please use V0.51 or later.

To anybody who reports "not working", please share the URL of the page that is not working. We will try our best to make it work for you.

Reviews

Recent review snapshot

Inspect the latest comments and rating distribution.

Store average score4.0Chrome Web Store aggregate rating, including ratings without synced review text
Synced text average3.7Average computed only from synced review bodies below
Reviews with text175Synced review bodies
Total ratings / reviews290Chrome Web Store public rating/review count

Store average score: 4.0. The bars below are calculated from synced review text only, so they may be empty for extensions that have public ratings but no synced comments yet.

5
99
4
11
3
15
2
10
1
40
Заочный Кружок2017年4月13日
5

Works perfectly. Text/Plain, really UTF-8, neither encoding info nor BOM. Brave New Chrome without your extension can do nothing with such content. Thank you!

Language en
0 helpful · 1 not helpful
陳紀芬2017年4月8日
5

有幫助 謝謝

Language zh
夏鸣松2017年4月5日
5

特别方便实用

Language zh
1 helpful · 0 not helpful
yoshihide takaesu2017年4月4日
5

とても助かりました! ありがとうございます。

Language ja
1 helpful · 1 not helpful
J. Collins2017年4月2日
3

Short version: Doesn't work on local files. Period. Works on websites otherwise. Long version: I got this extension explicitly for the local "WYSIWYG-compatible" HTML files I make for my stories (for my writing). These generally don't have <head> tags or the like, but up until recently, this generally didn't seem to be a problem for Chrome. Not sure what changed or when, but now, my HTML files are giving me garbage. (Guess Chrome's auto-detection needs work...) Unfortunately, as I found out from reading the Support tab for this addon... it was not designed... in any way, shape, or form... for local, offline files. That beig said, the addon is completely useless to me. However, the addon DOES work exactly as promised on live websites, so it DOES do what it says it does. Just... not in the way I want it to. Maybe some day, Google will fix auto-encoding or make UTF-8 the default when there's no information available. In the meantime... I guess I'll have to find a different solution to my problem... which is a darn shame, honestly... This is a really nice-looking addon.

Language en
2 helpful · 1 not helpful
KOT KALLIAK2017年3月31日
1

Не работает

Language ru
1 helpful · 0 not helpful
Lucas Lopez2017年3月29日
1

no sirve para nads

Language fil
1 helpful · 2 not helpful
寒枫(寒枫)2017年3月24日
5

添加这个插件后,右击网页,可以看到一个01的选择,就可以看到可以选择各种编码了

Language zh
小阮2017年3月23日
5

设置了好像没什么用?

Language zh
1 helpful · 0 not helpful
递归2017年3月22日
5

thanks

Language en
1 helpful · 0 not helpful