# Importing tilesets - bug or not supported yet?

**URL:** <https://discourse.mapeditor.org/t/importing-tilesets-bug-or-not-supported-yet/1268>\
**Category:** Bugs\
**Created:** [April 13, 2016, 9:33pm UTC](https://discourse.mapeditor.org/t/importing-tilesets-bug-or-not-supported-yet/1268 "2016-04-13T21:33:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anothergol](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@anothergol](https://discourse.mapeditor.org/u/anothergol)\
**Post date:** [April 13, 2016, 9:33pm UTC](https://discourse.mapeditor.org/t/importing-tilesets-bug-or-not-supported-yet/1268/1 "2016-04-13T21:33:49Z")

</div>

Edit: disregard this, I now understand how the feature works. So you press export, and the whole map is now linked to the tileset, and to edit it again, you import it back. Makes sense now, not intuitive but a good idea.

* * *

\_I can’t seem to be able to import tilesets. \_

_-the button to import tilesets looks disabled_

_-exporting works, but when you drag/drop a tileset file onto the editor, it doesn’t load the tileset, it’s just the image importer_

_This said, I don’t quite understand why tilesets are embedded in maps. Isn’t a tileset supposed to be shared among maps, thus the last thing you’d want is tiles not sharing their properties?_

---

<div class="post-metadata">

**Author:** ![bjorn](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.mapeditor.org/bjorn/32/1599_2.png) [@bjorn](https://discourse.mapeditor.org/u/bjorn)\
**Post date:** [April 14, 2016, 6:54am UTC](https://discourse.mapeditor.org/t/importing-tilesets-bug-or-not-supported-yet/1268/2 "2016-04-14T06:54:03Z")

</div>

Yes, I’m sorry the current workflow is not intuitive, but this part of Tiled is main thing I’m trying to improve for Tiled 1.0. It’s a hard problem to solve, but I think I’m getting somewhere. See the [March development update](http://forum.mapeditor.org/t/march-2016-development-updates/1164) for more information.

---

<div class="post-metadata">

**Author:** ![anothergol](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@anothergol](https://discourse.mapeditor.org/u/anothergol)\
**Post date:** [April 14, 2016, 10:13am UTC](https://discourse.mapeditor.org/t/importing-tilesets-bug-or-not-supported-yet/1268/3 "2016-04-14T10:13:33Z")

</div>

Well it’s not a bad idea, had it been in the documentation, I would have had no problem with it.

I’m reading you moved tileset editing to its own tab, that makes sense too.  
You tell about not being able to see the changes in a tileset on the map. Not a problem for me at all, but maybe if tabs could be pulled out as floating windows, I don’t know?

---

<div class="post-metadata">

**Author:** ![bjorn](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.mapeditor.org/bjorn/32/1599_2.png) [@bjorn](https://discourse.mapeditor.org/u/bjorn)\
**Post date:** [April 14, 2016, 11:33am UTC](https://discourse.mapeditor.org/t/importing-tilesets-bug-or-not-supported-yet/1268/4 "2016-04-14T11:33:16Z")

</div>

> [@anothergol](#):
>
> Well it’s not a bad idea, had it been in the documentation, I would have had no problem with it.

Documentation is another thing on the list for Tiled 1.0. I know it could have been sooner, but working on new features or fixing issues always seems more important or useful…

> [@anothergol](#):
>
> You tell about not being able to see the changes in a tileset on the map. Not a problem for me at all, but maybe if tabs could be pulled out as floating windows, I don’t know?

Yeah, I already thought about that as well, but it will require even bigger changes to the code. Still, it’s something to consider for later.