# So what's the real deal with cacheAsBitmap?

**URL:** https://forum.kirupa.com/t/so-whats-the-real-deal-with-cacheasbitmap/285824
**Category:** flash
**Created:** [April 7, 2009, 12:26am UTC](https://forum.kirupa.com/t/so-whats-the-real-deal-with-cacheasbitmap/285824 "2009-04-07T00:26:17Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![sekasi](https://avatars.discourse-cdn.com/v4/letter/s/5f8ce5/32.png) [@sekasi](https://forum.kirupa.com/u/sekasi)
#### Post date: [April 7, 2009, 12:26am UTC](https://forum.kirupa.com/t/so-whats-the-real-deal-with-cacheasbitmap/285824/1 "2009-04-07T00:26:17Z")

</div>

I tend to use it a lot. It’s a great help for increasing the overall performance of your application if you know where and when cacheAsBitmap will help.

There’s one thing that pisses me off with it though. Pixelsnapping.

A bitmap in flash can be set to auto, never or always for pixelsnapping. When you cache a sprite as a bitmap, it automatically becomes Pixelsnapping.ALWAYS.

What’s the deal with that. I don’t want pixelsnapping. It looks poo.

this obviously applies to anything with filters on it too since filters == cacheAsBitmap.

:sen: \<-- I needs you!