# Non-pixelated layer for guides

**URL:** <https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625>\
**Category:** Features\
**Created:** [July 24, 2024, 1:50pm UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625 "2024-07-24T13:50:53Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![nTu4Ka](https://community.aseprite.org/letter_avatar/ntu4ka/32/6_22734026db12803ebb3e059622ac3534.png) [@nTu4Ka](https://community.aseprite.org/u/nTu4Ka)\
**Post date:** [July 24, 2024, 1:50pm UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625/1 "2024-07-24T13:50:53Z")

</div>

Several times I felt the need to have some kind of guide lines that should be non-pixelated.  
Either with aim to do a quick sketch of overall form or just put the guides for the shapes on the image (e.g. where terminator should be).  
These lines should render independently of pixel grid and have antialiasing to be able to draw smooth curves.  
Existing Aseprite drawing tools (pencil, lines, shapes) can be used to draw them. User should be able to define line thickness and color (no need for advanced brush behavior).

Overall - would be awesome to have a layer that acts as a really basic image editor.

---

<div class="post-metadata">

**Author:** ![Pixilized](https://community.aseprite.org/user_avatar/community.aseprite.org/pixilized/32/18982_2.png) [@Pixilized](https://community.aseprite.org/u/Pixilized)\
**Post date:** [July 24, 2024, 3:01pm UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625/2 "2024-07-24T15:01:08Z")

</div>

For that, you could just draw something in a normal drawing program and import it as a reference layer, so there’s no need to add this.

---

<div class="post-metadata">

**Author:** ![nTu4Ka](https://community.aseprite.org/letter_avatar/ntu4ka/32/6_22734026db12803ebb3e059622ac3534.png) [@nTu4Ka](https://community.aseprite.org/u/nTu4Ka)\
**Post date:** [July 24, 2024, 7:29pm UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625/3 "2024-07-24T19:29:08Z")

</div>

Not very good UX:

1. More difficult to have alignment between the image and the reference. E.g. I created a sketch → I did some drawing in Aseprite → I want to add new guides to the sketch. Now I have to somehow combine drawing from Aseprite and original sketch. It’s a lot of hustle.  
In my specific situation I encountered following. I was drawing animation and after having overall shape and colors wanted to add some guides for shading. So I would need to export the frame → import into raster editor → draw guides → export guides → import in Aseprite. And if something changes I need to do it again. And for each frame. It’s not very user friendly design.
2. If I want to make adjustment - I need to use another program again.

Last point.  
When I was starting this topic - I noticed several similar already posted.  
So the feature does seem to be requested.

---

<div class="post-metadata">

**Author:** ![Pixilized](https://community.aseprite.org/user_avatar/community.aseprite.org/pixilized/32/18982_2.png) [@Pixilized](https://community.aseprite.org/u/Pixilized)\
**Post date:** [July 24, 2024, 9:54pm UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625/4 "2024-07-24T21:54:23Z")

</div>

Those are good points, but remember that Aseprite is a _pixel_ art editor, so it wouldn’t make much sense to program in a whole new drawing program just for better guide layers

---

<div class="post-metadata">

**Author:** ![nTu4Ka](https://community.aseprite.org/letter_avatar/ntu4ka/32/6_22734026db12803ebb3e059622ac3534.png) [@nTu4Ka](https://community.aseprite.org/u/nTu4Ka)\
**Post date:** [July 25, 2024, 10:07am UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625/5 "2024-07-25T10:07:57Z")

</div>

We have reference layers which are not pixelized and there is nothing wrong with having them in pixel editor.

You personally may not feel the need for it because your workflow is different.

There is nothing wrong in being a retrograde still it makes sense to make things better.

---

<div class="post-metadata">

**Author:** ![Ethan\_Buttazzi](https://community.aseprite.org/user_avatar/community.aseprite.org/ethan_buttazzi/32/3265_2.png) [@Ethan\_Buttazzi](https://community.aseprite.org/u/Ethan_Buttazzi)\
**Post date:** [July 26, 2024, 12:25am UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625/6 "2024-07-26T00:25:10Z")

</div>

vector guide layers would be the best option here, but it would still take a lot of effort to make a 2nd graphic engine for specific layers, just for guides, i would recommedn you just sketch phisically for now

---

<div class="post-metadata">

**Author:** ![nTu4Ka](https://community.aseprite.org/letter_avatar/ntu4ka/32/6_22734026db12803ebb3e059622ac3534.png) [@nTu4Ka](https://community.aseprite.org/u/nTu4Ka)\
**Post date:** [July 26, 2024, 10:16am UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625/7 "2024-07-26T10:16:17Z")

</div>

How is Reference Layer different? It seems to be drawn the way that can suit this.

---

<div class="post-metadata">

**Author:** ![Ethan\_Buttazzi](https://community.aseprite.org/user_avatar/community.aseprite.org/ethan_buttazzi/32/3265_2.png) [@Ethan\_Buttazzi](https://community.aseprite.org/u/Ethan_Buttazzi)\
**Post date:** [July 26, 2024, 8:13pm UTC](https://community.aseprite.org/t/non-pixelated-layer-for-guides/22625/8 "2024-07-26T20:13:34Z")

</div>

reference are basically projected canvases that you cant edit, aseprite doesnt handle well big canvases due to its nature, so regarless we would need a adjencent “graphics engine” to handle bigger resolutions properly, without compromising the current engine.
