IMDTouchKnowledge BaseShop main store

How-to

How to Convert a WinCC Project From 1024x768 to 800x600

HMI and touchscreens Published 6 min read

Short answer

WinCC has no tool that converts an existing 1024x768 project to 800x600 automatically: you set the smaller picture size, then move and resize objects screen by screen. Because both resolutions are 4:3, the runtime adapt option scales everything uniformly to 78.125% with no distortion - usable as an interim display, but do the manual relayout for a permanent station.

On this page
  1. What the size setting actually changes
  2. Prepare before you edit
  3. Convert the project picture by picture
  4. The numbers: scaling 1024x768 down to 800x600
  5. The adapt option is a display mode, not a conversion
  6. Verify on the real display
  7. Questions asked

No automatic conversion exists in classic WinCC: there is no tool that takes a finished 1024x768 project and re-lays it out at 800x600, and the picture size is meant to be chosen when the picture is created. The working method is to set the smaller size, move and resize objects picture by picture, and verify every screen at runtime on the real 800x600 display. One fact makes this pair easier than most downsizes: 1024x768 and 800x600 are both 4:3, so the runtime adapt option scales the whole picture uniformly to 78.125% with nothing distorted - enough to keep the station running while you do the actual conversion.

What the size setting actually changes #

A picture's size is its canvas. Changing it after the objects are drawn does not rescale them: every object keeps its pixel position and its pixel dimensions. Going from 1024x768 to 800x600 removes 224 px of width (1024 - 800) and 168 px of height (768 - 600), so anything placed in that right-hand and bottom band now sits outside the visible canvas, and the objects that remain have less room and can collide. That is why a layout breaks when the size is changed late, and why the size is best set when the picture is created.

The runtime side is configured per station, separately from the pictures: in classic WinCC, right-click Computer, open Properties, and on the Graphics Runtime tab set the Screen Resolution to what the display actually runs - 800x600 here. The size you edit into the pictures and the resolution the station expects have to agree, or a correctly edited project still scales or clips at runtime.

Prepare before you edit #

Copy the entire project and edit only the copy; the original is your rollback, because this change touches every picture. Then establish exactly what you have: the WinCC version, and confirmation that the project is classic WinCC rather than WinCC flexible or a TIA Portal project - the settings named in this article belong to classic WinCC. The discipline is the same one you use to verify the HMI project version running on a panel: know what is running before you change it. If the family is unclear, the toolchain differences are laid out in WinCC V7.4, WinCC Flexible 2008 and TIA Portal compared. Last, confirm the replacement station really displays 800x600 by checking the display settings of the runtime PC. Converting the project for a panel that actually runs 1024x768 just moves the problem.

Convert the project picture by picture #

  1. Copy the project and open the copy in the editor. The original stays untouched until the converted project has passed runtime verification.
  2. Set the station resolution: in WinCC Explorer, right-click Computer, Properties, Graphics Runtime tab, and set the Screen Resolution to 800x600.
  3. Start with the busiest picture, not the simplest one, and set its size to 800x600. The busiest screen exposes every problem the conversion has; a sparse screen proves nothing.
  4. Fix that picture: move every object out of the lost 224 px on the right and 168 px at the bottom, shrink only what must shrink, and keep each label next to its control. A uniform shrink of everything is the one move to avoid - it makes text and touch targets smaller everywhere instead of only where the smaller canvas demands it.
  5. Run that one picture at runtime on the 800x600 display before touching the rest. If the method holds on the hardest screen, it holds everywhere; if it fails, you have found out on one screen instead of all of them.
  6. Repeat the edit picture by picture. Screens with different layouts convert differently - a dense faceplate is not a trend screen, and a screen that converts cleanly proves nothing about the next one.
  7. Close with a full pass: navigate every screen, press every button and input field, and confirm nothing is clipped, overlapping, mislabeled or out of reach.

The numbers: scaling 1024x768 down to 800x600 #

Inputs: the designed project is 1024 x 768 px, the target display runs 800 x 600 px, and nothing else in the project changes.

The rule in words: the horizontal scale factor is the target width divided by the source width, and the vertical factor is the target height divided by the source height. If the two factors are equal, one uniform scale maps the whole picture onto the display with no distortion; if they differ, no single scale fits both axes.

The arithmetic:

  • Horizontal factor: 800 ÷ 1024 = 0.78125
  • Vertical factor: 600 ÷ 768 = 0.78125
  • The factors match because both resolutions are 4:3: 1024 ÷ 4 = 256 and 768 ÷ 3 = 256; 800 ÷ 4 = 200 and 600 ÷ 3 = 200.
  • Size reduction under scaling: 1 - 0.78125 = 0.21875, so every object renders at 78.125% of its designed size.
  • Canvas reduction under manual editing: 1024 - 800 = 224 px of width and 768 - 600 = 168 px of height no longer exist.

Result: one uniform factor of 0.78125 covers both axes. Nothing distorts; everything shrinks by 21.875%.

Decision: this gives you two thresholds, one per path. On the adapt path, enabling the option means accepting 78.125% of every object's size - so look at the smallest text and the smallest touch target on your busiest screen and judge them at that size on the real display; if they remain usable, the adapted display can serve permanently, and the first one that does not decides for the manual relayout. On the manual path the threshold is positional, not proportional: any object in the rightmost 224 px or the bottom 168 px of the old canvas must move, whatever its size.

The adapt option is a display mode, not a conversion #

Classic WinCC has an "Adapt picture" option in the computer properties, on the same Graphics Runtime tab, and WinCC Runtime Professional under TIA Portal has its documented equivalent under Runtime settings, Screens, Window behavior: enable "Adapt screen". Both scale the picture to the runtime window at display time, and neither changes what is stored in the project.

Because this pair shares the 4:3 aspect ratio, adaptation is geometrically clean here: the uniform 0.78125 factor calculated above, no stretching. Use it deliberately. Enable it on day one so the station keeps running and every tag stays reachable while you relayout picture by picture, and treat it as the permanent state only if the size check in the worked example passed. On a target with a different aspect ratio the two axis factors diverge and a single scale can no longer fit both; that failure mode does not exist between these two resolutions.

Verify on the real display #

The editor is not the proof; runtime behavior depends on the station's display configuration. Load the converted project on the actual 800x600 station and walk every screen: nothing clipped at the edges, no overlaps, labels attached to the correct controls, text legible, and every button and input field reachable and working.

Set the editor zoom to 100% when you judge geometry, so you see target pixels one to one, and if a screen looks wrong before you have changed anything, check the Windows display scaling on that PC first: a Windows font-scaling setting such as 125% changes how the editor renders the picture. Rule that out before you touch the project.

Questions asked

Is there a WinCC function that converts every screen at once?

No. The only project-wide mechanism is the runtime adapt option, and it is a display mode: the stored pictures stay at 1024x768 and are scaled every time they appear, so the project never becomes a native 800x600 project. That is why the conversion is done per picture, in the editor, with the objects moved by hand.

Does the same procedure apply to WinCC in TIA Portal?

The layout work is identical, but the settings live elsewhere. For an RT Advanced device you change the screen resolution in the Runtime settings of the HMI device. For Runtime Professional, the documented adaptation is under Runtime settings, Screens, Window behavior, where you enable Adapt screen. In both cases objects keep their geometry, so re-check every screen after the change.

Can the converted 800x600 project still run on the old 1024x768 monitor?

Yes, with the adapt option enabled, because the 4:3 geometry works in reverse: 1024 ÷ 800 = 1.28 and 768 ÷ 600 = 1.28, so the picture scales up uniformly to 128% with no distortion. Text grows instead of shrinking, so legibility is not the constraint; check fine lines and tightly spaced objects instead, because magnifying the picture magnifies every small misalignment.

Should I just redraw every screen at 800x600?

Not by default. Keep the objects that already fit, move what collides, and shrink only what must shrink. Redrawing is the answer for the individual screens whose layout is too dense to survive a 22% size cut or whose content sits mostly in the lost 224 x 168 px band - decide screen by screen, never project-wide.

Keep reading

  • How-to

    Convert an MT500 Project to EasyBuilder 8000 and Resize It

    EasyBuilder 8000 converts an MT500 .eob into a new .mtp project through the Tools menu; the converter selects the terminal with the nearest dimensions, so you must then select the real destination model on the Model tab and work through the resize dialog it triggers. Verify page geometry and live controller data before the panel returns to service.

    HMI and touchscreens

  • Troubleshooting

    E200 HMI recovery when the supplied file is a GOT project

    The E200 is an E-series terminal programmed with E-Designer, and it accepts only a native E-Designer project file with the .MPA extension. GT Designer3 opens GOT projects and can convert E-Designer projects toward the GOT, never the reverse, so recovery means obtaining the original .MPA from the machine builder or a backup, then downloading it over the documented serial cable.

    HMI and touchscreens

  • Comparison

    TIA Portal vs STEP 7 plus WinCC hardware configuration

    Configuring the same PLC and HMI in TIA Portal instead of STEP 7 plus WinCC needs no extra PLC, panel, module or network hardware — the cabinet stays exactly as it is. The difference is where devices, networks and tags are configured: one integrated project instead of two. The one hard limit: S7-1200 and S7-1500 CPUs engineer only in TIA Portal, and CPU firmware sets the minimum release, so a V2.9 CPU needs TIA Portal V17 or higher.

    HMI and touchscreens