You are viewing the documentation for the 2.5.x release series. The latest stable release series is 3.0.x.


WebSockets are sockets that can be used from a web browser based on a protocol that allows two way full duplex communication. The client can send messages and the server can receive messages at any time, as long as there is an active WebSocket connection between the server and the client.

Modern HTML5 compliant web browsers natively support WebSockets via a JavaScript WebSocket API. However WebSockets are not limited in just being used by WebBrowsers, there are many WebSocket client libraries available, allowing for example servers to talk to each other, and also native mobile apps to use WebSockets. Using WebSockets in these contexts has the advantage of being able to reuse the existing TCP port that a Play server uses.

Tip: Check to see more about which browsers supports WebSockets, known issues and more information.

§Handling WebSockets

Until now, we’ve been writing methods that return Result to handle standard HTTP requests. WebSockets are quite different and can’t be handled via standard Play actions.

Play provides two different built in mechanisms for handling WebSockets. The first is using actors, the second is using simple callbacks. Both of these mechanisms can be accessed using the builders provided on WebSocket.

§Handling WebSockets with actors

To handle a WebSocket with an actor, we need to give Play a object that describes the actor that Play should create when it receives the WebSocket connection. Play will give us an to send upstream messages to, so we can use that to help create the Props object:

import play.libs.F.*;
import play.mvc.WebSocket;
import play.mvc.LegacyWebSocket;
public static LegacyWebSocket<String> socket() {
    return WebSocket.withActor(MyWebSocketActor::props);

The actor that we’re sending to here in this case looks like this:


public class MyWebSocketActor extends UntypedActor {

    public static Props props(ActorRef out) {
        return Props.create(MyWebSocketActor.class, out);

    private final ActorRef out;

    public MyWebSocketActor(ActorRef out) {
        this.out = out;

    public void onReceive(Object message) throws Exception {
        if (message instanceof String) {
            out.tell("I received your message: " + message, self());

Any messages received from the client will be sent to the actor, and any messages sent to the actor supplied by Play will be sent to the client. The actor above simply sends every message received from the client back with I received your message: prepended to it.

§Detecting when a WebSocket has closed

When the WebSocket has closed, Play will automatically stop the actor. This means you can handle this situation by implementing the actors postStop method, to clean up any resources the WebSocket might have consumed. For example:

public void postStop() throws Exception {

§Closing a WebSocket

Play will automatically close the WebSocket when your actor that handles the WebSocket terminates. So, to close the WebSocket, send a PoisonPill to your own actor:

self().tell(PoisonPill.getInstance(), self());

§Rejecting a WebSocket

Sometimes you may wish to reject a WebSocket request, for example, if the user must be authenticated to connect to the WebSocket, or if the WebSocket is associated with some resource, whose id is passed in the path, but no resource with that id exists. Play provides a reject WebSocket builder for this purpose:

public LegacyWebSocket<String> socket() {
    if (session().get("user") != null) {
        return WebSocket.withActor(MyWebSocketActor::props);
    } else {
        return WebSocket.reject(forbidden());

Note: the WebSocket protocol does not implement Same Origin Policy, and so does not protect against Cross-Site WebSocket Hijacking. To secure a websocket against hijacking, the Origin header in the request must be checked against the server’s origin, and manual authentication (including CSRF tokens) should be implemented. If a WebSocket request does not pass the security checks, then acceptOrResult should reject the request by returning a Forbidden result.

§Accepting a WebSocket asynchronously

You may need to do some asynchronous processing before you are ready to create an actor or reject the WebSocket, if that’s the case, you can simply return CompletionStage<WebSocket<A>> instead of WebSocket<A>.

§Handling different types of messages

So far we have only seen handling String frames. Play also has built in handlers for byte[] frames, and JSONNode messages parsed from String frames. You can pass these as the type parameters to the WebSocket creation method, for example:

public LegacyWebSocket<JsonNode> socket() {
    return WebSocket.withActor(MyWebSocketActor::props);

§Handling WebSockets using callbacks

If you don’t want to use actors to handle a WebSocket, you can also handle it using simple callbacks.

To handle a WebSocket your method must return a WebSocket instead of a Result:

public LegacyWebSocket<String> socket() {
    return WebSocket.whenReady((in, out) -> {
        // For each event received on the socket,

        // When the socket is closed.
        in.onClose(() -> System.out.println("Disconnected"));

        // Send a single 'Hello!' message

A WebSocket has access to the request headers (from the HTTP request that initiates the WebSocket connection) allowing you to retrieve standard headers and session data. But it doesn’t have access to any request body, nor to the HTTP response.

When the WebSocket is ready, you get both in and out channels.

It this example, we print each message to console and we send a single Hello! message.

Tip: You can test your WebSocket controller on Just set the location to ws://localhost:9000.

Let’s write another example that totally discards the input data and closes the socket just after sending the Hello! message:

public LegacyWebSocket<String> socket() {
    return WebSocket.whenReady((in, out) -> {

§Configuring WebSocket Frame Length

You can configure the max length for WebSocket data frames using play.websocket.buffer.limit or passing -Dwebsocket.buffer.limit system property when running your application. For example:

sbt -Dwebsocket.buffer.limit=64k run

This configuration gives you more control of WebSocket frame length and can be adjusted to your application requirements. It may also reduce denial of service attacks using long data frames.

Next: The Twirl template engine

Found an error in this documentation? The source code for this page can be found here. After reading the documentation guidelines, please feel free to contribute a pull request. Have questions or advice to share? Go to our community forums to start a conversation with the community.