I think the difference is somewhat slight but actually really critical.
With REST, a common pattern is that you have our RESTful APIs return "business objects", but then down in the UI layer of the app you have a bunch of logic to turn these into "presentation objects". There are a couple problems with this:
1. If you have to support multiple front ends, like Android and iOS, you have to dupe all this logic.
2. If you have native apps, it makes it MUCH more difficult to change your backend APIs without breaking things.
3. Related to #2 above, GraphQL provides a much better paradigm for maintaining backwards compatibility than REST.
What other folks have said is somewhat true, with GraphQL a lot of what you do is "push up" code from the client up into the server. However, especially with native apps where you can't necessarily control when users upgrade, it is a huge benefit to be able to update that code serverside instead of clientside.