Actually there might be a solution here that you could try 😃   http://dl.ifip.org/db/conf/networking/networking2015/1570062089.pdf   " To identify the FQDNs used by the WhatsApp service, we rely on manual inspection of hybrid measurements. We actively generate WhatsApp text and media flows at end devices (both Android and iOS), and passively observe them at two instrumented access gateways. We especially paid attention to the DNS traffic generated by the devices. Not surprising, our measurements revealed that WhatsApp servers are associated to the domain names whatsapp.net (for supporting the service) and whatsapp.com (for the company website). In addition, different third level domain names are used to handle different types of traffic (control, text messages, and multimedia messages). Control and text messages are handled by chat servers associated to the domains {c|d|e}X.whatsapp.net (X is an integer changing for load balancing), whereas multimedia contents are handled by multimedia (mm) servers associated to the domains mmsXYZ.whatsapp.net and mmiXYZ.whatsapp.net for audio and photo transfers, and mmvXYZ.whatsapp.net for videos. As we see next, chat and mm servers have very different network footprints. While connections to chat servers are characterized by low data-rate and long duration (specially due to the control messages), media transfers are transmitted in short and heavy flows. "   From this article it looks like you could block say images or videos specifically, but allow things like text messages etc. I have a feeling this is how airliners do it now that I discovered this.   So I 'think' that if you block the following:   mm*.whatsapp.net* pp*.whatsapp.net*   Then you won't be able to send media, but texts should still work.  In theory of course. ... View more