# Wrong "frame" values in JSON

**URL:** https://community.aseprite.org/t/wrong-frame-values-in-json/4445
**Category:** Bug Reports
**Created:** [December 18, 2019, 5:34am UTC](https://community.aseprite.org/t/wrong-frame-values-in-json/4445 "2019-12-18T05:34:41Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Tarragon](https://community.aseprite.org/letter_avatar/tarragon/32/5_5575768a8748004e209b776fc1b2916d.png) [@Tarragon](https://community.aseprite.org/u/Tarragon)
#### Post date: [December 18, 2019, 5:34am UTC](https://community.aseprite.org/t/wrong-frame-values-in-json/4445/1 "2019-12-18T05:34:41Z")

</div>

Some of the “frame” values in the exported JSON are wrong.

I am using the macOS Steam build, v1.2.16.3.

Please find a ZIP containing the Aseprite doc, the exported files, and a screenshot of my export settings [here](https://drive.google.com/file/d/1Ov8xsh_PVrdOPzbK9-JSBxeD6xkjrXrg/view?usp=sharing).

If you search the JSON for “test-02 (aaa) 0.aseprite,” you’ll see that its frame values are 0, 0, 20, 21 – which are correct. However, the values for “(aaa) 1” are 0, 0, 256, 256 – which are incorrect. I’m not sure if it has to do with linked frames… However, a different layer – “(bbb)” – also uses linked frames and doesn’t appear to have this problem.