null Skip to main content

GF 223 - 6 Mil Matte White

Item#Item NameRegular PriceSale PriceQty

GF 223 is a 6.0 mil matte white semi-rigid vinyl with a removable acrylic pressure sensitive adhesive on a 90# liner. This vinyl is designed to accept a variety of solvent-based, UV curable and latex inks common to wide format digital printing systems. GF 223 is a removable decal film designed for ease of application of temporary interior or exterior signage, decals, nameplates, die cut letters and point-of-purchase displays. Semi-rigid films are easy to handle due to their rigidness and thus can be applied quickly.

 

APPLICATIONS

  • General Signage
  • POP & Indoor Signage
  • Windows

INK COMPATIBILITY

  • Solvent
  • Eco-Solvent
  • Latex
  • UV Curable
  • Screen
  • Offset (UV Curable)

 

Can I use GF 223 on other surfaces?

GF 223 works great with flat, smooth surfaces. It is a great solution for temporary store front applications requiring bond to windows.
 

What if I leave GF 223 on past it’s optimal removability time frame?

GF 223 will always be removable, but you may have some percentage of adhesive transfer when left on past the 1 year clean removal timeline.
 

Can this product be used on Elevators?

These types of doors may have a clear coat or other type of protection. This product is not designed for coated/sealed/treated stainless steel, brass or bronze surfaces. It is best to contact the facility manager and determine the best product for this application.
// 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