Tawk.to is free and easy to add a live chat widget to your site. However, its branding is too aggressive and some customers may find it disturbing when initiating the chat.
Here’s the screenshot of the branding I’m talking about.
Remove tawk.to branding
Since this chat widget is added via JavaScript, the display none CSS trick won’t work here.
There are a couple of ways to remove it.
- (RECOMMENDED) Purchasing the Remove Branding add-on, which also gives you the option to use your own domains for your chat page.
- (FREE) Adding a PHP Code Snippet to your site which can be found below:
add_action( 'wp_footer', static function() {
?>
<script>
setInterval( findTawkAndRemove, 100 );
function findTawkAndRemove() {
let parentElement = document.querySelector("iframe[title*=chat]:nth-child(2)");
if ( parentElement ) {
let element = parentElement.contentDocument.querySelector(`a[class*=tawk-branding]`);
if ( element ) {
element.remove();
}
}
}
</script>
<?php
});The Code Snippet can be added to your theme’s (preferably child theme’s) functions.php file. Alternatively, an easier way is to use the Code Snippets plugin.
I hope this helps! If you have any questions, let me know in the comments.
How to remove tawk.to branding in WordPress
Wow. Great. Thanks Aryal
This method works like charm! Thanks!
works briefly and then the whole chat freezes
Thanks for reaching out. Is there any live site URL to look into the issue you’re describing?
You can test pruebashabs.company.site here is it it works like a couple of senconds then if you press the top left size of the chat and get out of it and then enter again and then out it freezes
*side
yep as that guy said, it is not working the chat windows freezes after a couple of minutes thanks for the effort though
Thanks for reporting and testing. I’ll make a note to look into the codes later. Currently, I don’t have any other ideas.
thank you, for taking the time to reply and look into it. we’ll be in touch
Excellent, thank you Sanjeev Aryal!
after some time it freeze
unfortunately, it’s a known issue. If I find any other way, I’ll update the code snippet.