# Linked files to improve team work flow

**URL:** <https://community.aseprite.org/t/linked-files-to-improve-team-work-flow/21833>\
**Category:** Features\
**Created:** [April 2, 2024, 7:28am UTC](https://community.aseprite.org/t/linked-files-to-improve-team-work-flow/21833 "2024-04-02T07:28:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ahrimanes](https://community.aseprite.org/user_avatar/community.aseprite.org/ahrimanes/32/14095_2.png) [@ahrimanes](https://community.aseprite.org/u/ahrimanes)\
**Post date:** [April 2, 2024, 7:28am UTC](https://community.aseprite.org/t/linked-files-to-improve-team-work-flow/21833/1 "2024-04-02T07:28:43Z")

</div>

Imagine working with 2 artist. each one have its own tasks for the same character. working in a single file is a mess… so what about linked files? where each artist work on his own tasks on his own file, then there is a file where we can link both files, and then export sprite sheets, even edit frames on them and this change will be updated on the original file, and soo if wee keep editing original files it will be updated on the linked one…

---

<div class="post-metadata">

**Author:** ![dacap](https://community.aseprite.org/user_avatar/community.aseprite.org/dacap/32/10_2.png) [@dacap](https://community.aseprite.org/u/dacap)\
**Post date:** [April 7, 2024, 1:28pm UTC](https://community.aseprite.org/t/linked-files-to-improve-team-work-flow/21833/2 "2024-04-07T13:28:43Z")

</div>

Hi @ahrimanes, the tilemap feature [#977](https://github.com/aseprite/aseprite/issues/977) contains a future work to allow using external tilesets (linking files) in a tilemap layer:

 ![image](https://community.aseprite.org/uploads/default/original/3X/7/8/7852bb3bf40145914e8098826a73e39672737b5e.png)

There are a similar plans for palettes [#4313](https://github.com/aseprite/aseprite/issues/4313).

I think the tilemap with external tilesets will be the initial work for a future [composition of external subsprites](https://github.com/aseprite/aseprite/issues/593) which was unplanned some time ago but probably is the starting point for a possible Aseprite v1.4.
