What is the difference between screen with resolution 2560*1440 with zoom - 200% and screen with resolution 1280*720?

It looks like you are referring to "zoom 200%" in some OS settings.

When you use 1280*720 everything is rendered in this resolution and then scaled up as a bitmap (by your monitor). The final image indeed consists of 2x2 pixel blocks.

When you use 2560*1440 resolution with zoom of 200% then every object is scaled up first, then rendered in the full resolution. With a bitmap it may not make a difference but objects like TrueType fonts or vector graphics scale "smoothly", they can alter every available pixel separately. In effect the resulting image doesn't necessarily form 2x2 pixel blocks on your screen as in the first case.


Example

  1. Let's start with low resolution 4x4:

    grid4

  2. We draw an object described as "upper-left right triangle, 4x4, black":

    triangle4 on grid4

  3. The monitor gets the above bitmap and scales it to its native resolution 8x8, so each original pixel becomes a 2x2 pixel block:

    triangle4 scaled

  4. Now let's use 8x8 resolution from the very beginning:

    grid8

  5. We consider an object described as "upper-left right triangle, 4x4, black":

    triangle4 on grid8

  6. But we tell the OS to use 200% zoom. The OS recalculates the object and gets "upper-left right triangle, 8x8, black":

    trinagle8 on grid8

    This is then sent to the monitor and displayed.

Comparison:

triangle4 scaled trinagle8 on grid8

Note if we only had the original 4x4 triangle as a bitmap, the final result would be like the left one above, regardless if the scaling was done by the OS or the monitor. Mathematical description of the triangle allowed the OS to recalculate it to new dimensions and get the smooth image at the end.

In modern operating systems many GUI elements, fonts etc. are available as "mathematical descriptions" that may be recalculated smoothly to given dimensions (zoomed). The general term is vector graphics.


In addition to Kamil's excellent answer (graphics and text will be drawn at the improved resolution and therefore look better), MacOS and iOS actually allow the developer to use different artwork depending on the screen resolution. On a zoomed display, you may use artwork with additional details that wouldn't be readable on a lower quality display, and use artwork with fewer details for lower quality screens.

For example, in a word processor you might have an icon to create numbered lists. On a high resolution screen, that icon contains tiny numbers 1, 2, 3 which are just about readable. If that was scaled down to a low resolution screen, it would just be a blur, so for low resolution a hand designed lower resolution icon is used.


Your first image has 2511x1151 pixels. The fonts are clearly rendered to the full resolution rather than half-resolution, so your "200% zoom" concerns just the rendering scale rather than its contents (unless, of course, the content is only available as a bitmap in the original resolution). Your image is better than you expected it.

Now assuming that we scale up prerendered content (I can do this on my desktop using ALT-scroll rather than CTRL-scroll but don't know how prevalent that may be on desktops other than XFCE), you might encounter the opposite situation: that prerendered content looks worse than at original scale.

In that case, you might be seeing the effects of subpixel rendering. In a nutshell, red, green, and blue subpixels are on slightly different locations and subpixel rendering incorporates this information for rendering shapes that are slightly better than those rendered without that knowledge. Of course, when scaling up or printing or viewing on a screen with different color specifics, the subpixel relation of the rendering intent is no longer valid and the results may look worse than what you'd want to.

In a way, this is a variant of the "blocky" look when rendering on a device with more exactly rectangular pixels than what the intended display device was.