Click here to Skip to main content
Click here to Skip to main content

ViewState Compression

, 10 Jul 2006 CPOL
Rate this:
Please Sign up or sign in to vote.
How to compress the ViewState of ASP.NET pages and save bandwidth.


Recently, I developed a huge ASP.NET page, with more than 30 controls. As we all know, it's a good idea to disable the ViewState for the controls that don't actually need it, say Literals or Labels. After doing that, I noticed that the hidden ViewState field was still a few KBs big. This is obviously a big problem for the users that still don't have a broadband connection, because uploading 40 KB to the server is really a bad issue, especially when they begin to click the "Submit" button again and again because they don't notice any response. So, after a few searches through the Internet, I built a simple solution to compress the ViewState and therefore save a rough 50% of the bandwidth. This post by Scott Hanselman has been particularly useful. Although it's possible to use external libraries to perform compression tasks, I think the better solution is to use the GZipStream or DeflateStream that the .NET Framework 2.0 includes.

Compressing and Decompressing Data in Memory

First of all, we need a way to compress and decompress an array of bytes in memory. I put together this simple static class that exposes two methods: Compress and Decompress. The two available classes, GZipStream and DeflateStream, according to MSDN, use the same algorithm, so it's irrelevant which one you choose.

The code below is really simple, and doesn't need further explanation:

using System.IO;
using System.IO.Compression;

public static class Compressor {

  public static byte[] Compress(byte[] data) {
    MemoryStream output = new MemoryStream();
    GZipStream gzip = new GZipStream(output, 
                      CompressionMode.Compress, true);
    gzip.Write(data, 0, data.Length);
    return output.ToArray();

  public static byte[] Decompress(byte[] data) {
    MemoryStream input = new MemoryStream();
    input.Write(data, 0, data.Length);
    input.Position = 0;
    GZipStream gzip = new GZipStream(input, 
                      CompressionMode.Decompress, true);
    MemoryStream output = new MemoryStream();
    byte[] buff = new byte[64];
    int read = -1;
    read = gzip.Read(buff, 0, buff.Length);
    while(read > 0) {
      output.Write(buff, 0, read);
      read = gzip.Read(buff, 0, buff.Length);
    return output.ToArray();

You need to save this class in a .cs file and put it in the App_Code directory of your ASP.NET application, making sure it's contained in the proper custom namespace (if you don't specify any namespace, the class will be available in the built-in ASP namespace).

Compressing the ViewState

Now, we can actually compress the ViewState of the page. To do that, we have to override the two methods LoadPageStateFromPersistenceMedium and SavePageStateToPersistenceMedium. The code simply uses an additional hidden field, __VSTATE, to store the compressed ViewState. As you can see, by viewing the HTML of the page, the __VIEWSTATE field is empty, while our __VSTATE field contains the compressed ViewState, encoded in Base64. Let's see the code.

public partial class MyPage : System.Web.UI.Page {

  protected override object LoadPageStateFromPersistenceMedium() {
    string viewState = Request.Form["__VSTATE"];
    byte[] bytes = Convert.FromBase64String(viewState);
    bytes = Compressor.Decompress(bytes);
    LosFormatter formatter = new LosFormatter();
    return formatter.Deserialize(Convert.ToBase64String(bytes));

  protected override void SavePageStateToPersistenceMedium(object viewState) {
    LosFormatter formatter = new LosFormatter();
    StringWriter writer = new StringWriter();
    formatter.Serialize(writer, viewState);
    string viewStateString = writer.ToString();
    byte[] bytes = Convert.FromBase64String(viewStateString);
    bytes = Compressor.Compress(bytes);
    ClientScript.RegisterHiddenField("__VSTATE", Convert.ToBase64String(bytes));

  // The rest of your code here...

In the first method, we just decode from Base64, decompress and deserialize the content of the __VSTATE, and return it to the runtime. In the second method, we perform the opposite operation: serialize, compress, and encode in Base64. The Base64 string is then saved into the __VSTATE hidden field. The LosFormatter object performs the serialization and deserialization tasks.

You may also want to create a new class, for example, CompressedPage, inheriting from System.Web.UI.Page, in which you override the two methods and then inherit your page from that class, for example MyPage : CompressedPage. Just remember that .NET has only single inheritance, and by following this way, you "spend" your only inheritance chance to use the ViewState compression. On the other hand, overriding the two methods in every class is a waste of time, so you have to choose the way that best fits your needs.

Performances and Conclusions

After a few tests, I noticed that the ViewState has been reduced from 38 KB to 17 KB, saving 44%. Supposing you have an average of 1 postback per minute per user, you could save more than 885 MB of bandwidth per month on every single user. That's an excellent result: you save bandwidth (and therefore money), and the user notices a shorter server response time.

I wanted to point out that this solution has a performance hit on the server's hardware. Compressing, decompressing, encoding, and decoding data is quite a heavy work for the server, so you have to balance the number of users with your CPU power and RAM.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Dario Solera

Italy Italy
Software Development Manager working on IaaS cloud computing. Cloud believer, (former) entrepreneur, F1 addict.

Follow me at or on Twitter.
Follow on   Twitter   Google+

Comments and Discussions

QuestionViewstate issue with SharePoint PinmemberPiranF30-Dec-14 21:32 
QuestionHow do you do this with masterpages? Pinmemberolaleke11-Feb-14 1:39 
AnswerRe: How do you do this with masterpages? Pinprofessionaladriancs3-Jun-14 21:12 
QuestionProblem!! [modified] PinmemberMember 1005975420-Jun-13 8:04 
AnswerRe: Problem!! PinmemberMember 1005975420-Jun-13 8:46 
GeneralMy vote of 5 Pinmemberamadou daffe5-Dec-12 8:56 
QuestionNot sure that problem exists in a first place PinmemberGeorge20142-Sep-12 20:05 
AnswerRe: Not sure that problem exists in a first place Pinmemberboros2419-Sep-12 7:30 
AnswerRe: Not sure that problem exists in a first place Pinmemberamit@123456710-Dec-12 22:45 
GeneralMy vote of 5 PinmemberCarlos Mattos (MVP)14-Aug-12 10:18 
QuestionNaming & performance PinmemberMalay Thakershi1-Aug-12 13:43 
GeneralMy vote of 5 Pinmemberlunabi668-Feb-11 3:27 
GeneralMy vote of 5 PinmemberE.F. Nijboer22-Oct-10 13:34 
QuestionCompression generates even bigger viewstate, why? Pinmemberjrbosch4-Feb-10 13:21 
AnswerRe: Compression generates even bigger viewstate, why? PinmemberShadowDanser16-Jan-11 4:13 
GeneralOptimize code Pinmembertruongpham17-Oct-09 8:07 
GeneralRe: Optimize code PinmemberE.F. Nijboer22-Oct-10 13:33 
QuestionExcellent!!! but have some problems with UserControls Pinmemberinharry17-Sep-09 11:33 
GeneralSuperb! Pinmemberkjerolran5-Mar-09 11:23 
Generaldoubt in above article PinmemberMaha_M15-Jun-08 6:40 
QuestionMemory leak? Pinmemberlrwilson4-Jun-08 4:59 
AnswerRe: Memory leak? PinmemberDario Solera7-Jun-08 7:12 
GeneralCompression and Ajax Pinmembermdmasonmbcs14-Apr-08 6:22 
GeneralRe: Compression and Ajax PinmemberTim McCurdy14-Jan-09 3:53 
GeneralRe: Compression and Ajax PinmemberMninawa18-Aug-10 4:25 
GeneralRe: Compression and Ajax PinmemberTim McCurdy18-Aug-10 4:59 
Generalgood stuff Pinmembermrkyle28-Feb-08 19:39 
GeneralExcellent Article..!! PinmemberSujith John Thomas21-Jul-07 3:18 
GeneralAnother way [modified] Pinmemberboros2422-Feb-07 4:13 
GeneralRe: Another way PinmemberMunsifali Rashid28-Oct-07 12:02 
GeneralRe: Another way PinmemberFahad Azeem25-Apr-08 6:47 
GeneralASP.NET AJAX 1.0 Problem Pinmemberlookaround15-Feb-07 3:48 
GeneralRe: ASP.NET AJAX 1.0 Problem PinmemberDAJG10-Jul-07 9:06 
GeneralRe: ASP.NET AJAX 1.0 Problem Pinmemberuyildir11-Nov-07 11:08 
GeneralRe: ASP.NET AJAX 1.0 Problem PinmemberCoolVini7-Oct-08 0:16 
GeneralRe: ASP.NET AJAX 1.0 Problem Pinmemberkjerolran5-Mar-09 11:02 
GeneralRe: ASP.NET AJAX 1.0 Problem Pinmemberdhejov15-Aug-10 20:39 
GeneralVB.Net version using ICSharpCode.SharpZipLib Pinmemberaka200527-Nov-06 9:26 
Great article.[^]
Questiondose it make server busy? Pinmemberhuobazi@aspxboy.com25-Nov-06 7:02 
AnswerRe: dose it make server busy? Pinprofessionaladriancs3-Jun-14 21:14 
GeneralExcellent. Pinmemberdeepaks328-Aug-06 22:13 
GeneralServer Side Pinmemberjonavi18-Jul-06 3:08 
GeneralRe: Server Side PinmemberDario Solera18-Jul-06 3:24 
GeneralRe: Server Side Pinmemberjonavi18-Jul-06 3:29 
GeneralRe: Server Side PinmemberDario Solera18-Jul-06 3:36 
GeneralRe: Server Side Pinmemberjonavi18-Jul-06 3:38 
GeneralRe: Server Side PinmemberDario Solera18-Jul-06 3:47 
GeneralRe: Server Side Pinmemberjonavi18-Jul-06 4:38 
GeneralRe: Server Side PinmemberDario Solera18-Jul-06 22:46 
GeneralRe: Server Side Pinmemberjonavi18-Jul-06 4:16 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web03 | 2.8.150414.1 | Last Updated 10 Jul 2006
Article Copyright 2006 by Dario Solera
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid