When a client requests a resource, the server sends the resource along with an ETag. On subsequent requests for the same resource, the client can include the ETag in the HTTP header. The server checks the ETag and, if the resource hasn't changed, it can respond with a 304 Not Modified status, saving bandwidth and reducing load times.