null Skip to main content

GF 204 - 3 Mil Gloss White, Clear low-tack removable adhesive

Item#Item NameRegular PriceSale PriceQty

GF 204 is a 3.4 mil polymeric gloss white calendered vinyl coated with a clear low-tack removable acrylic pressure sensitive adhesive laminated to a 90# layflat liner. This vinyl is designed to accept a variety of solvent-based, eco-solvent, latex and UV curable inks common to wide format digital printing systems. The clear adhesive creates a lasting bond to a variety of common substrates yet will remove easily and cleanly at the end of the useful life of the graphic. The 90# liner offers excellent product layflat in a variety of ambient conditions.

 

APPLICATIONS
  • General Signage
  • POP & Indoor Signage
  • Windows
INK COMPATIBILITY
  • Solvent
  • Eco-Solvent
  • Latex
  • UV Curable
  • Screen
  • Offset (UV Curable)

 

What applications is GF 204 intended for?

GF 204 is designed for temporary interior or exterior signage, decals, nameplates, die-cut letters and point-of-purchase displays. Not designed for coated/ sealed/ treated stainless steel, brass or bronze surfaces.
 

How long can GF 204 be applied to windows?

GF 204 is rated for 1 year clean removability. If the vinyl is left on for longer, it will not adversely affect the glass surface, but may be harder to remove, including the possibility of adhesive transfer.
// Uses React's native (unpatched) value setter + a real dispatched event, // so the app's own onChange / validation / append logic fires correctly. // build the visible field the user will actually type into // copy the real field's classes + computed styles so it looks identical // preload with existing value (formatted) if the real field already has one // hide the real field visually but keep it in the DOM and functional, // so your app's own validation / append event still works as before // place the visible field right where the real one used to be // send only the plain digits to the real field — this matches what // the numeric field type expects, so no "invalid phone number" error // keep focus/blur events flowing to the real field too, in case your // app's validation triggers specifically on those