Welcome to EasyEDA. Well done for asking for help to check a footprint that you are unsure about. :) When asking about components please help others to help you by posting a link to the item datasheet rather than leaving it to others to have to go looking for it. [https://www.sparkfun.com/datasheets/Prototyping/Connectors/JST(2)-01548.pdf](https://www.sparkfun.com/datasheets/Prototyping/Connectors/JST%282%29-01548.pdf)<br> <br> Please also read **How to create findable footprints and searchable symbols**, (2.3) in (2) in: [https://easyeda.com/forum/topic/How-to-ask-for-help-and-get-an-answer-71b17a40d15442349eaecbfae083e46a](https://easyeda.com/forum/topic/How-to-ask-for-help-and-get-an-answer-71b17a40d15442349eaecbfae083e46a)<br> <br> to learn about the importance of clearly naming and describing symbols and footprints that you have modified or created. It also describes several other aspects of the correct way to modify or create symbols and footprints including how to set the origin of the component in the right place. You have assumed that the User created part is for the part that you have chosen but it has no clearly identifying name and no description of the part that so you actually have no idea which component it is supposed to represent. There is however a link in the footprint to the JST connector page which includes the link above to the datasheet which shows that the user contributed footprint is pretty much completely wrong for the part it is intended to represent. The pad hole size and spacing (or pitch) in your modified but identically named and also completely undescribed part is correct but the silkscreen outline is still incorrect for the part that is shown in the datasheet. You need to read and understand the dimensional drawing in the datasheet and draw a correctly dimensioned outline that also clearly shows the pad positions within it. Please post back for another round of checking it when you have read the links above and had another go at creating a clearly identified, well described, dimensionally correct-to-the-datasheet footprint. :)