Kode Injector FAQ

Kode Injector maps website hostnames to local JavaScript and CSS files. When you open a matching website, it reads the files you configured and applies their current contents automatically.

Check that the rule hostname matches the current page, each path points to an existing local file, the rule and required file toggles are enabled, the current site is not disabled in the popup, and global injection is not paused.

No enabled rule matches the current page hostname. Open Kode Injector Options and create a rule for that site, or confirm that an existing rule uses the correct hostname.

Open the browser’s extension details for Kode Injector, enable “Allow access to file URLs”, return to Options, and select “Check again”. Also confirm the path is an absolute local path or a valid file:/// URL.

No. Browser-managed file access is the default and simplest method. The read-only Native Helper is an optional advanced alternative in Chrome and Edge, while Firefox requires it.

Yes. A rule needs at least one source file, but the other field can be left empty. JavaScript and CSS can also be enabled or disabled independently after the rule is created.

The Helper reads only explicitly requested local regular files up to 5 MiB. It cannot write files, list directories, execute programs, start subprocesses, or access the network.

No. It has no developer-operated backend or analytics service. Rules, preferences, hostnames, file paths, and file contents remain on the user’s device unless the configured code itself sends data from the target page.

Yes. Selected CSS is inserted into the page and JavaScript runs in the page’s main world. The configured website can inspect or process that code, so use only trusted local code on websites you trust.

Helper updates are manual. Download the package for your platform from GitHub Releases and follow its installer instructions. On macOS, open Kode Injector Helper and choose Reinstall, Repair, or Uninstall before moving the app to Trash.