GITNUXSOFTWARE ADVICE
Digital MarketingTop 10 Best Email Signature Services of 2026
Top 10 email signature services ranked for teams, with comparisons including Rocketseed, Xink, and Exclaimer to pick the best fit.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Rocketseed is the best fit if you want centralized, brand-consistent email signatures with governed rollouts across many users, whereas Upwork is the better alternative when you need a custom build where contractors handle the signature work for your team.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Rocketseed
Rule-based signature deployment that standardizes HTML blocks and plain-text output across mail clients under one change workflow.
Built for fits when teams need centralized signature governance with consistent mobile rendering and managed rollout workflows..
Xink
Editor pickTemplate version control with enforced centralized rollout helps maintain consistent signature content after policy changes.
Built for fits when mid-market and enterprise teams need controlled, directory-driven signature rollouts across many mailboxes..
Exclaimer
Editor pickRule-driven, conditional signature templates combined with server-side insertion for consistent rendering and controlled deployment.
Built for fits when centralized control and scalable deployment matter for many departments and changing rules..
Related reading
Comparison Table
Rocketseed
enterprise_vendorCloud-hosted email signature software providing centralized brand-consistent signatures with marketing campaign tracking.
Rule-based signature deployment that standardizes HTML blocks and plain-text output across mail clients under one change workflow.
Rocketseed’s core capability is centralized signature management that drives consistent HTML email signature blocks and legal footers across many mailboxes. The service is built around managed deployment rather than local user editing, which improves governance when multiple departments own different signature components. Plain-text fallback handling supports compatibility across clients that do not render complex HTML consistently.
A tradeoff is that Rocketseed’s value depends on configuring templates, rules, and asset handling up front, so teams with ad hoc per-user edits may see more process than flexibility. It works best when signature enforcement matters, such as when HR, Sales, and Support need different blocks under consistent brand guidelines.
- +Server-side signature insertion keeps output consistent across clients
- +Centralized template control reduces cross-team signature drift
- +Mobile-aware rendering supports legibility on small screens
- +Change workflows improve signature version control across releases
- –Requires upfront template and rules configuration for governance
- –Approval flows can add cycle time for rapid one-off edits
- –Asset handling needs clear ownership to avoid broken logos
- –Debugging rendering issues requires time on representative clients
IT and email operations teams
Enforce signatures across all mailboxes
Lower support tickets
Marketing and brand teams
Maintain brand-compliant signature templates
Consistent brand presentation
Show 2 more scenarios
Sales enablement teams
Roll out team-specific contact cards
Fewer signature inconsistencies
Managed templates support consistent contact-card layouts with reliable fallback text.
HR and compliance teams
Apply legal footer uniformly
Lower compliance risk
Central footer rules reduce omissions and keep disclaimer text consistent.
Best for: Fits when teams need centralized signature governance with consistent mobile rendering and managed rollout workflows.
More related reading
Xink
enterprise_vendorCloud email signature platform with centralized management, directory integration, and multi-client deployment.
Template version control with enforced centralized rollout helps maintain consistent signature content after policy changes.
Xink is a fit for organizations that need governance over signature blocks, including contact-card content, brand assets, and legally required footer sections. The service centers on centralized configuration so updates can propagate across users without redesigning messages manually. Directory synchronization and mail flow insertion patterns reduce drift between templates and real user signatures.
A key tradeoff is that getting clean results depends on disciplined template structure and asset preparation, especially when teams maintain different signature variants. Xink works best when a dedicated owner coordinates version control of signature content and when rollout timing matters for an org-wide change.
- +Centralized template governance reduces signature drift across large orgs
- +Directory synchronization supports consistent user assignment at scale
- +HTML signature handling includes dependable plain-text fallback
- +Versioned signature updates support controlled rollout changes
- –Template complexity can slow first rollout for segmented teams
- –Asset preparation requirements increase effort for logo and card elements
- –Some advanced personalization needs stronger admin process discipline
- –Rendering test coverage can require deliberate setup time
IT and email operations
Enforce consistent signatures via directory
Fewer signature inconsistencies
Brand and marketing ops
Standardize templates across divisions
Aligned brand footer content
Show 2 more scenarios
Sales enablement teams
Roll out contact-card updates quickly
Cleaner contact handoffs
Distributes consistent vCard-style contact elements so reps share accurate details.
Compliance and legal teams
Manage disclaimer and footer blocks
Reduced compliance gaps
Keeps legal footer content centralized so updates apply uniformly across the organization.
Best for: Fits when mid-market and enterprise teams need controlled, directory-driven signature rollouts across many mailboxes.
Exclaimer
enterprise_vendorEnterprise email signature management software for centralized design, deployment, and governance across Microsoft 365 and Google Workspace.
Rule-driven, conditional signature templates combined with server-side insertion for consistent rendering and controlled deployment.
Exclaimer is well suited for centralized signature governance where multiple departments contribute content but leadership needs consistent branding and compliance. Centralized signature management reduces drift because templates and rules are authored once and applied through controlled deployment. Server-side signature insertion helps keep rendering consistent even when email clients vary in how they handle HTML and plain-text fallback.
A practical tradeoff is that Exclaimer’s flexibility comes with rule planning, especially when conditional logic overlaps across teams. It fits best when an IT or marketing ops team needs directory synchronization for user mapping and wants repeatable signature deployment rather than per-user editing.
- +Server-side signature insertion keeps output consistent across email clients
- +Directory synchronization supports scalable user and group scoping
- +Template rules handle conditional content for teams and locations
- +Signature testing supports safer rollouts before broad enforcement
- –Complex conditional logic needs careful governance to avoid conflicts
- –Advanced layouts can require iterative tuning for different client behaviors
- –Cross-team approval workflows may still rely on external process discipline
- –Hosted assets handling can add overhead for frequent brand changes
IT governance teams
Enforce signatures across many mailboxes
More consistent signature compliance
Marketing operations teams
Localize signatures by office and department
Better relevance per recipient
Show 2 more scenarios
Help desk and email administrators
Reduce per-user signature support
Fewer manual signature edits
Uses directory synchronization to map users and groups automatically for updates.
Compliance and legal teams
Standardize legal footers
Lower compliance drift
Keeps disclaimer text consistent through centralized templates and controlled rollout testing.
Best for: Fits when centralized control and scalable deployment matter for many departments and changing rules.
SignatureSatori
enterprise_vendorEmail signature management tool for Google Workspace with centralized template design and directory synchronization.
Signature version control tied to governance and analytics reporting, making it easier to track what was deployed and what rendered.
SignatureSatori focuses on centralized email signature management for organizations that need consistent HTML signature blocks across users. It provides template-based signature creation with controlled deployment behavior for Microsoft 365 and other common enterprise email environments.
SignatureSatori also supports recurring governance workflows like approval of signature content changes and repeatable rollout patterns across teams. For measurement, it includes signature analytics that connect rendered signature activity to specific assets and versions.
- +Centralized template governance keeps signature markup consistent across teams
- +Signature analytics report activity by asset and signature version
- +Workflow support for approval and repeatable rollout of signature updates
- +Works well for environments that need enforced signature consistency
- –More administrative setup is required for multi-team template variations
- –Some advanced personalization depends on specific data sources and mappings
- –Testing signature rendering takes extra steps across email clients and devices
- –Complex brand rules can increase template and approval overhead
Best for: Fits when enterprise teams need governed, versioned signatures with analytics and controlled rollouts.
Bybrand
enterprise_vendorEmail signature management platform offering branded template creation and centralized deployment for businesses.
Template-driven signature governance with controlled rollout of signature versions across users.
Bybrand generates and centrally manages HTML email signature blocks and deploys them across an organization’s email ecosystem. It focuses on configuration and governance for signature templates, including brand assets and reusable signature components.
Administration includes controls for who gets which signature versions and how changes roll out. The strongest fit appears in environments that need consistent formatting across clients and repeatable signature deployment workflows.
- +Centralized signature template management for consistent HTML rendering
- +Reusable brand assets and signature blocks reduce manual updates
- +Versioned rollouts support controlled signature change management
- +Integration pathways fit organizations that manage identities at scale
- –Workflow setup takes disciplined ownership across IT and marketing
- –Fine-grained per-user overrides can require extra configuration work
- –Testing signature rendering across mobile clients needs deliberate effort
- –Analytics and click tracking depth may lag workflow-first competitors
Best for: Fits when centralized signature governance and repeatable template rollouts matter more than one-off custom formatting.
Patronum
enterprise_vendorGoogle Workspace management platform including email signature standardization alongside directory and user lifecycle tools.
Approval-driven signature publishing with centralized template updates for consistent governance at scale.
Patronum is an email signature management service built around hosted signature templates and automated deployment to user mailboxes. It supports HTML signatures with plain-text fallback so the same governance workflow covers both rich and minimal rendering paths.
Patronum also emphasizes operational controls like approval workflows and centralized configuration, so changes stay consistent across teams. The service fits organizations that need controlled signature updates across many users with repeatable rollout behavior.
- +Centralized template management reduces per-user signature drift
- +Rich and plain-text outputs cover common client rendering gaps
- +Hosted asset handling supports consistent logos across mail clients
- +Workflow controls support review and governed publishing
- –Signatures require setup in each target environment for enforcement
- –Advanced targeting increases configuration steps for admins
- –Legacy clients can still show formatting differences despite fallback
- –Testing and approval cycles add overhead for frequent changes
Best for: Fits when enterprises need governed signature rollout across many users and multiple mail clients.
CodeTwo
enterprise_vendorEmail signature management add-ons and cloud services for Microsoft 365 environments with directory-synced signature templates.
Rules-driven deployment with signature testing lets admins validate rendering and targeting before enforcing rollout.
CodeTwo focuses on centralized email signature governance with server-side insertion options for Microsoft 365 and Exchange environments. The product supports signature templates, centralized management, and rules-based deployment so signatures and legal footers can be applied consistently across users.
CodeTwo also includes client-side delivery choices and testing workflows that help validate rendering before broader rollout. For organizations that need change control across multiple signature blocks, CodeTwo provides versioned configuration and deployment logic rather than per-user manual edits.
- +Centralized signature governance with rules for targeted deployment
- +Server-side and client-side insertion options for different mail flows
- +Signature testing workflows reduce rollout surprises across clients
- +Granular template control for multi-block signatures and legal footers
- –Rules and deployment scope need careful planning to avoid mismatches
- –Advanced rollout workflows require more admin time than template-only tools
- –Directory synchronization breadth depends on the chosen deployment path
- –Mobile rendering checks add extra steps for complex signatures
Best for: Fits when Microsoft 365 or Exchange teams need managed, rules-based signature rollout and controlled governance.
Upwork
freelance_platformUpwork provides access to independent designers and developers for custom email signature projects.
Marketplace access to specialized signature designers and developers for bespoke signature templates and client-specific rendering requirements.
Upwork is primarily a freelance marketplace, not an email-signature management product, so email-signature delivery happens through hired specialists and custom build work. The service can cover signature design, HTML and plain-text variants, and operational handoff for deployment across email clients by engaging experienced designers and developers.
Centralized signature governance, directory synchronization, and server-side insertion controls are not a native Upwork capability, so outcomes depend on the contractor’s toolchain. Integration depth and automation surface therefore vary by contractor, with the strongest results coming from clearly specified signature templates and deployment requirements.
- +Breadth of independent HTML signature designers for quick template iterations
- +Ability to commission bespoke disclaimer blocks and contact-card layouts
- +Access to developers who can wire insertion approaches for email workflows
- +Contracted work can tailor signatures to brand guidelines and asset constraints
- –No built-in centralized signature management or enforcement controls
- –Directory synchronization and identity-based governance require custom delivery
- –Signature testing and version control processes depend on contractor discipline
- –Automation and API surface vary widely across hired teams
Best for: Fits when a team needs custom email-signature builds and contractor-managed deployment work.
Freelancer
freelance_platformFreelancer lets businesses hire independent professionals for email signature design, coding, and implementation work.
Hosted signature template deployment mapped to freelancer account identities to keep signature changes tightly aligned to user records.
Freelancer handles HTML email signature work through hosted signature templates and server-side insertion workflows for participating freelancer accounts. It focuses on templated signature blocks with brand assets like logos and contact-card content, plus consistent formatting across email clients.
The core delivery model is template management tied to account identities, with limited depth for enterprise governance compared with dedicated email-signature suites. Automation is oriented around deploying and updating signature templates rather than offering granular policy control for signature enforcement at scale.
- +Template-driven signature blocks that keep formatting consistent across updates
- +Hosted signature asset support for logos and branded images
- +Identity-tied deployment model for freelancer account workflows
- +Plain-text fallback capability for basic readability in constrained clients
- –Limited admin governance depth versus enterprise email-signature platforms
- –Fewer controls for signature version control and staged rollout workflows
- –Click tracking and analytics are not a core emphasis in standard signatures
- –Extension points for deep directory synchronization and policy automation are limited
Best for: Fits when freelancer teams need quick, template-based signature updates with light administration.
DesignCrowd
freelance_platformDesignCrowd sources custom graphic design concepts from a global community of freelance designers.
Commissioning ability for custom signature visuals and brand assets through contest or freelance submissions.
DesignCrowd is a market research and creative services site rather than an email signature management service. It offers design contest work, not centralized signature governance, server-side or transport-rule insertion, or identity-provider based provisioning.
Its signature-related output is limited to assets and templates produced through freelance workflows, not ongoing enforcement or version control. Teams needing HTML email signature rendering, plain-text fallbacks, and deployment testing must use a dedicated signature platform.
- +Good option for commissioning logo and signature artwork assets
- +Freelance marketplace workflow can produce custom layout drafts
- +Contest-style sourcing can generate multiple signature concept options
- +Useful for getting brand-aligned graphics when brand guidelines exist
- –No centralized signature management or governance for employees
- –No signature insertion engine for Exchange, Microsoft 365, or Google Workspace
- –No signature analytics, click tracking, or UTM generation
- –No automated signature version control or rendering test workflow
Best for: Fits when teams need outsourced signature artwork or HTML mockups, not managed email signature enforcement.
Conclusion
After evaluating 10 digital marketing, Rocketseed stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right email signature
Email signature services centralize HTML signature templates and rules so email clients receive consistent rich-text and plain-text output instead of per-user edits. This guide covers Rocketseed, Xink, Exclaimer, SignatureSatori, Bybrand, Patronum, CodeTwo, and also includes Upwork, Freelancer, and DesignCrowd.
The key differences across these providers come from centralized governance workflows, server-side versus client-side insertion support, and how template rollout and testing are handled for large mailboxes and many departments. Rocketseed leads for rule-based deployment that standardizes HTML blocks and plain-text output under one change workflow, while Xink and Exclaimer focus on enforced rollout with directory synchronization for scalable assignments.
Email signature management that enforces consistent HTML and plain-text output across mail clients
An email signature is the branded signature block appended to outbound messages, often including disclaimers, contact-card elements like vCard style fields, and embedded images with alt text. Signature systems typically generate both rich-text and plain-text fallback so mobile and desktop clients render the intended content.
Rocketseed uses rule-based signature deployment that standardizes HTML blocks and plain-text output across mail clients under one change workflow, which reduces cross-team signature drift. Exclaimer applies rule-driven, conditional signature templates with server-side insertion so email output stays consistent across clients and departments while directory synchronization scopes which users and groups receive each signature set.
Email signature capabilities that affect governance and rendering consistency
Centralized signature governance matters because Rocketseed, Xink, Exclaimer, SignatureSatori, and Bybrand all manage templates and rollout instead of letting users edit signatures per mailbox. Rendering consistency matters because server-side insertion options keep HTML and plain-text output aligned across mobile and desktop clients, which is a differentiator called out in Rocketseed and Exclaimer.
Rule-based deployment with standardized HTML and plain-text output
Rocketseed deploys rule-based signatures that standardize HTML blocks and plain-text output across mail clients under one change workflow. Exclaimer also uses rule-driven templates with server-side insertion to keep output consistent across clients and departments.
Directory synchronization for scalable user and group scoping
Xink and Exclaimer include directory synchronization so administrators can scope signatures by user and group at scale. Exclaimer combines directory synchronization with rule-driven conditional templates for department-level control.
Template version control and governed rollout tracking
Xink enforces template version control with centralized rollout so policy changes stay consistent after deployment. SignatureSatori ties signature version control to governance and analytics reporting by asset and signature version.
Approval and controlled publishing workflows for multi-team changes
Patronum uses approval-driven signature publishing with centralized template updates to control rollout across many users and multiple mail clients. Bybrand provides centralized signature template management with controlled rollout of signature versions across users.
Signature testing before enforcement to reduce mis-targeted deployments
CodeTwo includes rules-driven deployment with signature testing so admins validate rendering and targeting before enforcing rollout. Rocketseed focuses on one change workflow standardization, which reduces drift but still requires governance discipline in template and rule setup.
Insertion model coverage across mail flows with admin governance
CodeTwo supports both server-side and client-side insertion options for different mail flows in Microsoft 365 or Exchange environments. Rocketseed emphasizes server-side insertion for consistent output, which can simplify governance when a single enforcement model is preferred.
Admin and workflow constraints for organizations that need governance depth
SignatureSatori requires more administrative setup for multi-team template variations while still providing governance and analytics. Patronum adds configuration steps for enforcement by requiring setup in each target environment for signature enforcement.
Choose an email signature platform based on rollout control, enforcement approach, and admin workflow fit
Start by matching the rollout model to the way signature changes actually get approved in the organization. Rocketseed and Exclaimer emphasize change workflows that standardize output, while Patronum focuses on approval-driven publishing for governed multi-team updates.
Next, pick the enforcement and testing posture that fits the risk tolerance for mis-targeting and rendering differences. CodeTwo adds signature testing before enforcement, while Xink and SignatureSatori emphasize version control and governance tracking for template changes at scale.
Map the required change workflow to a platform rollout style
If signature changes move through a centralized rule change process, Rocketseed standardizes HTML blocks and plain-text output under one change workflow. If changes require multi-team approval gates, Patronum uses approval-driven signature publishing with centralized template updates.
Select the enforcement and insertion coverage that matches the mail flow environment
If Microsoft 365 or Exchange mail flows need a choice between server-side and client-side insertion, CodeTwo offers both insertion options. If the priority is consistent output across clients using server-side insertion, Exclaimer and Rocketseed both emphasize server-side signature insertion.
Decide whether the directory is the source of truth for assignment
If signatures must be scoped by user and group from your directory, Xink and Exclaimer include directory synchronization. If the deployment model is driven more by centralized template and rules than by directory scoping, Rocketseed still relies on centralized governance with rule-based deployment.
Choose the level of template version control and rollout tracking
If audits and rollback-style management depend on template versioning tied to governance, Xink and SignatureSatori both provide template version control with governed rollout. If signature governance requires visibility into what rendered by version and asset, SignatureSatori’s analytics reporting by asset and signature version is built for that.
Plan for testing and deployment validation before enforcing across many mailboxes
If reducing mis-targeted deployments matters, CodeTwo includes signature testing so admins can validate rendering and targeting before enforcing rollout. If risk is managed through strict centralized template control and a standardized output approach, Rocketseed’s governance reduces cross-team drift but still requires upfront template and rules configuration.
Assess whether setup effort fits the operating model for logo, cards, and personalization
If fine-grained personalization and asset mapping increase implementation effort, Xink highlights asset preparation requirements for logo and card elements. If your organization expects more admin overhead for multi-team template variation, SignatureSatori calls out the need for more administrative setup for multi-team template variations.
Who should buy an email signature service like Rocketseed, Xink, or Exclaimer
Email signature governance is a direct operational control for organizations that send high-volume outbound email with multiple departments, because signatures must stay consistent across many mailboxes and clients. Centralized signature rollout also fits teams that need measurable control over deployed content, which is why SignatureSatori and CodeTwo focus on version control and pre-enforcement testing.
Enterprises with many departments that need consistent HTML and plain-text rendering
Exclaimer and Rocketseed both emphasize server-side signature insertion for consistent output across email clients. Exclaimer adds conditional templates plus directory synchronization for department-level scoping.
Mid-market and enterprise teams that manage templates as policy artifacts
Xink enforces template version control with centralized rollout to keep signature content consistent after policy changes. SignatureSatori adds analytics reporting tied to signature version and asset activity for governed deployments.
Microsoft 365 and Exchange administrators who need testing before enforced rollout
CodeTwo includes signature testing so admins can validate rendering and targeting before enforcement. CodeTwo also provides server-side and client-side insertion options depending on the mail flow.
Organizations that require approval workflows for controlled publishing at scale
Patronum is built around approval-driven signature publishing with centralized template updates for governed rollout. Bybrand provides centralized template management with controlled rollout, but Patronum’s approval model is the explicit fit for gated publishing.
Teams that need custom signature design work without centralized enforcement
Upwork and DesignCrowd enable commissioned bespoke signature visuals and assets through marketplace or contest workflows. These options do not provide built-in centralized signature management or an insertion engine for Exchange, Microsoft 365, or Google Workspace.
Common email signature buying mistakes that cause rollout failures or governance drift
The first failure mode is choosing a tool for template editing when the real need is enforced deployment consistency across mail clients. Rocketseed, Exclaimer, and CodeTwo all emphasize insertion and deployment control, while Upwork and DesignCrowd focus on commissioning rather than enforcement.
The second failure mode is underestimating governance setup effort for conditional rules, segmented templates, and multi-environment enforcement. Xink, SignatureSatori, and Patronum each flag specific setup and workflow complexity that affects time-to-rollout.
Buying a service that can draft signatures but not enforce them across the mail flow.
Upwork and DesignCrowd provide commissioning workflows for signature artwork or HTML mockups, but Upwork and DesignCrowd do not offer a signature insertion engine for Exchange, Microsoft 365, or Google Workspace. CodeTwo, Exclaimer, and Rocketseed are built around insertion and governed rollout control.
Skipping testing and validating targeting logic for segmented rules.
CodeTwo includes signature testing so admins can validate rendering and targeting before enforcing rollout. Exclaimer and Rocketseed can standardize output with rule governance, but complex conditional logic in Exclaimer still requires careful governance to avoid conflicts.
Underestimating template complexity and admin setup needed for multi-team rollout variations.
SignatureSatori requires more administrative setup for multi-team template variations, which can slow governance changes across teams. Xink highlights template complexity that can slow first rollout for segmented teams.
Treating directory sync as optional when assignment must match users and groups.
Xink and Exclaimer use directory synchronization to scope signatures across many mailboxes by user and group. Without directory-driven assignment, teams often resort to manual mailbox mapping that increases signature drift.
How We Selected and Ranked These Providers
We evaluated each provider on features depth and measured rollout control mechanisms, then weighted those capabilities at 40%. Ease and day-to-day admin overhead were weighted at 30%, and value for operational governance was also weighted at 30%.
Rocketseed earned the top position because rule-based signature deployment standardizes HTML blocks and plain-text output under one change workflow, which directly reduces cross-team signature drift. Rocketseed also rated highly on features and overall performance with an overall score of 9.5 And a features score of 9.7, Which aligned with the strongest governance and consistency workflow among the set.
Frequently Asked Questions About email signature
Which service provides the most consistent HTML and plain-text rendering across multiple mail clients?
How does server-side signature insertion change deployment and troubleshooting compared with client-side insertion?
When should signature governance be handled with template version control and approval workflows?
Which option best supports multi-department rollouts with directory synchronization and scoping?
What breaks if a signature platform lacks plain-text fallback for minimal clients and legacy systems?
Where does each service fall short for organizations that need signature analytics tied to specific assets and versions?
How does centralized RBAC-like administration typically work when multiple teams request different signature blocks?
When does a marketplace or creative services workflow become a poor fit for ongoing signature enforcement?
How should admins validate rendering before rolling signatures to all users?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Digital Marketing alternatives
See side-by-side comparisons of digital marketing tools and pick the right one for your stack.
Compare digital marketing tools→