Simple and Transparent Pricing
Choose the plan that fits your needs
Free usage
Perfect for discovering NGTextEditor and small projects
- All tools available locally
- 500 words limit in production
- No time limit on usage
Need more features?
Annual licensePro
PopularIdeal for small projects or freelancers
- 1 site / 1 project
- All NGTextEditor 2.0 features
- Updates included during license
- Standard support (ticket / email)
- Access to full documentation
Enterprise
For multi-site projects and teams
- Up to 3 sites / projects
- All advanced features
- Priority support
- Advanced integration guides
- Early access to new features
FAQ - NGTextEditor
Everything you need to know
When the license expires, NGTextEditor switches to degraded mode.
In this mode:
- the editor remains usable
- existing content remains accessible and editable
- certain advanced features (called "premium") are disabled
- a message indicates that the license is no longer active
This allows you to continue working without a sudden block, while clearly signaling the need for renewal.
Disabled features may include, depending on the plan:
- certain advanced layout tools
- advanced customization options
- premium insertion or styling tools
The exact list is documented to ensure complete transparency.
No. Renewal is never mandatory.
However, to regain all features and continue receiving updates and support, renewal is necessary.
No, by default. Renewal is manual to avoid any surprises.
Automatic renewal may be offered as an explicit option.
The annual license includes:
- full access to features corresponding to your plan
- updates during the validity period
- support associated with your chosen plan
No. NGTextEditor is entirely self-hosted.
No data is sent to any third-party service.
Because total freedom in a content editor almost always leads to inconsistent content, difficult to maintain and costly to fix.
The block system allows you to:
- structure content from the moment of creation
- avoid wonky layouts
- guarantee faithful and predictable rendering
You write freely within blocks, but you can no longer break the overall structure.
It is intentionally guided, but not constraining.
Users:
- write like in any modern editor
- use clear and consistent tools
- no longer experience unpredictable behavior
The constraint is there to prevent errors, not to block creativity.
No.
NGTextEditor is based on simple and explicit concepts:
- a text block to write
- a media block to insert visuals
- a clear grid for layout
Onboarding is quick because the behavior is logical and consistent.
In NGTextEditor, everything that is allowed always works correctly.
What is intentionally prevented:
- makeshift styles
- layouts impossible to maintain
- behaviors that break brand guidelines
It's not a loss of freedom, it's securing your product.
NGTextEditor is designed for the entire ecosystem:
- for users: reliable and consistent behavior
- for product teams: controlled rendering
- for developers: clean and stable HTML
Good code is not a technical luxury, it's a quality guarantee for the end user.
NGTextEditor doesn't lock you in.
You can:
- export content as HTML
- export content as structured JSON
- keep all structure and data intact
Your content remains usable, readable, and maintainable.
Yes.
Thanks to the JSON configuration file, you can:
- enable or disable tools
- limit available styles
- lock the configuration to ensure consistency
The same editor can be simple for a blog, strict for a business app.
NGTextEditor is for those who want to:
- produce clean and lasting content
- avoid technical debt from classic WYSIWYG editors
- maintain control over their brand image
It's not a "catch-all" editor. It's a professional editor.
Because it:
- prevents errors before they become costly
- structures content without complicating writing
- protects your product in the long term
Fewer surprises. Fewer fixes. More control.
Traditional WYSIWYG editors prioritize editing freedom at the expense of generated HTML quality.
Frequent result:
- Overloaded DOM
- Uncontrolled inline styles
- HTML difficult to maintain
- Technical debt with each product evolution
NGTextEditor takes the opposite approach: content must be structurally clean from creation.
NGTextEditor generates HTML that is:
- Semantically readable
- Structurally stable
- Without chaotic inline styles
- Consistent across sessions and users
Layout is based on:
- A clear grid
- Explicit blocks
- Exploitable data attributes (data-*)
Generated HTML is predictable and debuggable.
The block structure enforces:
- Clearly defined containers
- Distinct responsibilities (text / media)
- Clear separation between content and style
Customization is done:
- Via global CSS
- Via JSON configuration file
- Without depending on arbitrary user decisions
CSS remains centralized and controlled.
It is deliberately deterministic.
The rigidity:
- Prevents invalid combinations
- Guarantees future content compatibility
- Makes exports reliable
Content structured today remains usable tomorrow.
Yes, via the ngTextEditor-config.json file.
It allows:
- Enabling/disabling tools
- Restricting styles
- Locking configuration
- Applying strict brand guidelines
The same editor can serve: a business back-office, an editorial CMS, a B2B SaaS application.
No.
NGTextEditor is:
- Vanilla JavaScript
- No external dependencies
- Integrable into any stack (Symfony, Laravel, React, Vue, etc.)
No technological lock-in.
Two formats are available:
- HTML for direct display
- Structured JSON for storage, versioning, or transformation
JSON preserves:
- Block hierarchy
- Metadata
- Complete document structure
Content becomes exploitable data, not an HTML blob.
NGTextEditor is:
- Lightweight
- No dependencies
- No unnecessary DOM overhead
The block structure:
- Reduces recalculations
- Avoids unpredictable manipulations
- Facilitates future optimizations
Controlled performance, even on complex content.
Yes.
- HTML export
- JSON export
- PDF printing
No opaque proprietary data. No trapped formats.
That's precisely its core target.
NGTextEditor is designed for:
- Controlled environments
- Non-technical users
- Strong requirements for consistency and maintainability
Where classic WYSIWYG editors become a problem, NGTextEditor becomes a solution.
Yes.
In NGTextEditor:
- You write normally
- You format text with simple tools
- You see the final result immediately
You're not doing technical work, you're writing content.
Blocks are for organizing content, not complicating writing.
- A text block for writing
- A media block for images, videos, tables
- Each element in its place
Result: clearer, more readable, better presented content.
No.
You can:
- Start by writing
- Add or move blocks afterwards
- Adjust layout when content is ready
The system adapts to your way of working, not the other way around.
Because what you see on screen must remain:
- Readable
- Consistent
- True to brand image
NGTextEditor prevents:
- Wonky layouts
- Inconsistent styles
- Content that displays poorly elsewhere
It's not a limit, it's protection.
Yes.
With NGTextEditor:
- What you see is what will be displayed
- No surprises at publication
- No difference between users
Rendering is stable, reliable, and predictable.
Yes.
NGTextEditor automatically cleans copied content:
- No parasitic styles
- No broken formatting
- Conversion to clean blocks
You save time without polluting content.
Yes.
Media are integrated in dedicated blocks, with:
- Resizing
- Borders
- Simple visual options
No need to tinker, everything is planned.
No.
NGTextEditor is designed to:
- Prevent visual errors
- Avoid irreversible layouts
- Secure your content
You can write and modify without stress.
You can:
- Undo/redo
- Preview content
- Adjust blocks at any time
Nothing is final, nothing is lost.
For everyone who wants to:
- Write efficiently
- Produce clean content
- Avoid problems after publication
Whether you're a writer, communicator, marketer, or support, the tool remains simple and reliable.
- Fewer visible constraints
- Fewer surprises at publication
- More daily peace of mind
You write. The tool takes care of the rest.
NGTextEditor is designed to reduce the risk surface related to content editing.
It intentionally limits:
- unpredictable behaviors
- uncontrolled insertions
- inconsistent HTML structures
Less arbitrary freedom = fewer error vectors.
Content is:
- structured in blocks
- generated according to strict rules
- without free injection of arbitrary tags
The clear separation between:
- structure
- content
- style
greatly reduces risks related to free HTML editing.
The block model prevents the creation of dangerous or ambiguous structures.
No.
Users:
- don't edit raw HTML
- don't insert scripts
- only have access to explicitly authorized tools
All authorized behavior is defined upfront.
Yes.
Via the JSON configuration file, you can:
- enable or disable each tool
- restrict available styles
- lock the client-side configuration
The editor can be configured according to a principle of least privilege.
Yes.
NGTextEditor allows:
- enforcing color palettes
- limiting fonts
- blocking user settings
Visual rendering becomes compliant by design, not by post-correction.
Yes, via structured JSON export.
This format allows:
- analyzing the exact content structure
- identifying used blocks
- verifying style compliance
- enabling automated controls
Content becomes auditable, not just displayable.
Indirectly, yes.
NGTextEditor:
- collects no user data by default
- depends on no third-party service
- transmits nothing externally
Data stays within your application perimeter.
GDPR management then depends on your server implementation, but the editor adds no hidden risk.
No.
NGTextEditor:
- runs in vanilla JavaScript
- no CDN
- no third-party API
- no implicit telemetry
No uncontrolled outbound traffic.
Yes.
The operation is:
- deterministic
- reproducible
- documented
The generated structure is:
- readable
- stable
- exploitable by analysis or validation tools
No "magic" or opaque behavior.
Yes, particularly:
- business applications
- internal back-offices
- regulated tools
- demanding B2B environments
Where free editing is a risk, NGTextEditor provides control.
Because it reduces risks related to content editing by enforcing a clear, controllable, and auditable framework.