Simple user interface, powerful automation


Ease-of-use, for increased efficiency

ByteBlower is an all-in-one solution that can be controlled from any client desktop or laptop through an intuitive GUI. The GUI boasts a low learning curve, quick setup times and clear reports.

The GUI also comes with a command line interface. This allows a first and easy way to perform automation with ByteBlower: you can create a project with the GUI and run the test scenarios from the command line, without any need to start the GUI.

UI Download

GUI Version 2.10.0 (Changelog )

CLT Download

Command Line Tool (CLT) Version 2.10.0 (Changelog )


You can find example projects on our GitHub account. GUI examples on Github


While the GUI allows an easy yet flexible way of testing, the scripting API controls every bit and byte of your traffic test.

The ByteBlower scripting API comes with more than just the interface. A lot of examples are available, together with a higher-layer API and helper methods.



Version 2.10.0 (Changelog )

Mac OSX Windows Linux 64bit Linux 32bit


Over the years we've created a lot of examples in TCL. You can find them on our GitHub account.

TCL API examples on Github

Python beta


Version 2.10.0 (Changelog ) for python 2.7

Mac OSX Windows Linux 64bit Linux 32bit

Python examples on Github

Documentation online

The reference of our API is online available at following location. Here you will find all the methods that are available for automation.

TCL API documentation

Tool: ByteBlower Remote Capture

byteblower-remote-capture is a command line tool which enables the user to start and stop captures on a ByteBlower server. The result will be saved on the local PC.


Version 2.9.0

Mac OSX Windows Linux 64bit Linux 32bit

Note: Rx and Tx capture only supported on servers running version 2.9. Prior systems capture only RX


Argument name Description Notes
--server, -s The (remote) ByteBlower server to capture on.  
When this option is not given, localhost will be used. (handy for use on a ByteBlower server)
--interface, -i The name of the ByteBlower interface to capture on.
Examples: trunk-1-1, nontrunk-1
--out, -o The name of the file in which the results must be stored.  Only PCAP is supported for now.
Warning: If the given file name already exists, the file will be overwritten!
--filter, -f A well formed BPF capture filter to use.  This can be used to only select a portion of the incoming data optional
--snaplen Snaplen in bytes ( Note: Supprted since ByteBlower server 2.9 ) optional


  • byteblower-remote-capture --server --interface nontrunk-1 --filter "ip host and ip host" --out example1.pcap
  • byteblower-remote-capture --server --interface trunk-1-1 --filter "ip host and udp dst 1000" --out example2.pcap

Tutorials and example projects

Improve your skills

We to help you!

Wish more info?

contact us at