White-label your editor: hide the footer
Word count, Suggest a feature, Report a bug, version number: four switches on your license key. Turn them off and the editor ends where your UI ends. No code change, no redeploy.
- React
- Next.js
- Vue
- Angular
- Svelte
- Vanilla JS
- Laravel
- Bold
- Italic
- Heading
- List
- Link
- Image
The setup
Eddyter works as a white-label rich text editor: the strip under the editor (live word and character count, Suggest a feature, Report a bug and the version number) is four switches on your license key. Turn them off and the editor ends where your UI ends. Nothing in your code changes.
Hide the footer from your license key
- Open your license keys and pick the key your app uses.
- Scroll to Editor footer.
- Toggle off what your customers shouldn't see: Word & character count (the live counter on the left), Suggest a feature (the feedback link), Report a bug (the bug report link) and Version number (the build number on the right).
- Save, then refresh the page running the editor. The items you turned off are gone. No code change, no redeploy.
Hide only what you need
Each item is its own switch. In the video, the word count, Suggest a feature and Report a bug are turned off while the version number stays on.
Same package, two keys
Each license key carries its own settings. Leave the counter on for your internal writers, and strip the footer entirely on the key behind the surface your customers see.
Also on the license key page
Your key list with usage and renewal, plus the HTML view, locked-feature and recent-images settings. See the docs for every option and pricing for plans. The package is npm install eddyter, published on npm.
The config
| Feature | State | Why |
|---|---|---|
| Bold | On | Customers expect basic emphasis even in a stripped-down, white-labelled editor. |
| Italic | On | Pairs with bold for everyday emphasis without adding toolbar clutter. |
| Heading | On | Lets users structure longer notes so the output reads cleanly in your UI. |
| List | On | Bullet and numbered lists cover most customer-written content like steps and checklists. |
| Link | On | Users link to their own docs and pages; links render as plain anchors in your HTML. |
| Image | On | Lets customers drop screenshots and images in without leaving your product. |
The code
// app/Editor.tsx — Next.js app router
// Footer items (word count, Suggest a feature, Report a bug, version)
// are set on the license key in your dashboard. No prop, no redeploy.
"use client";
import { ConfigurableEditorWithAuth, EditorProvider } from 'eddyter';
import 'eddyter/style.css';
export default function Editor() {
return (
<EditorProvider>
<ConfigurableEditorWithAuth
apiKey={process.env.NEXT_PUBLIC_EDDYTER_KEY}
initialContent="<p>Hello, Eddyter!</p>"
onChange={(html) => console.log(html)}
/>
</EditorProvider>
);
}Grab your key from https://eddyter.com/user/license-key.
What this config produces
Welcome to the team, Priya
Your first week is planned below. Reply in this thread if anything needs to move.
Week one
- Monday: laptop setup and accounts with IT
- Tuesday: product walkthrough with your manager
- Wednesday: shadow two customer calls
- Friday: first 1:1 and goals for the month
Written in your app's editor, with no word counter, feedback links or version number underneath. Just your UI.
Questions
Do I need to change my code to hide the editor footer?
No. The footer is controlled by switches on your license key. Save the change and refresh the page running the editor; there is no code change and no redeploy.
Which footer items can I hide?
Four: the word and character count, the Suggest a feature link, the Report a bug link, and the version number. Each one is a separate switch, so you can hide some and keep others.
Can my internal tool and my customer-facing app show different footers?
Yes. Footer settings belong to each license key, so you can keep the word counter on one key for internal writers and hide the whole footer on the key your customers use.
Keep going
Not on the list?
Eddyter is a plug-and-play React component. If your product has a text box in it, the integration is the same ten minutes. Tell us what you are building and we will write the study for it.