null Skip to main content

GF 102 - 3 Mil Matte Clear, Clear Permanent Adhesive

Item#Item NameRegular PriceSale PriceQty

GF 102 is a 3.0 mil matte clear pressure sensitive vinyl laminate with a permanent acrylic adhesive on a smooth 53# liner. This calendered vinyl laminate protects graphics from abrasion and moisture. GF 102 is best applied by the cold laminating process without the addition of heat and is designed to protect digital and screen printed images for exhibit and display graphics. GF 102 can be used in most instances where an overlay with a matte finish is required on interior or exterior applications.

APPLICATIONS

  • General Signage
  • POP & Indoor Signage
  • Backlit Signage
  • Walls
  • Transit Advertising

INK COMPATIBILITY

Not Applicable

 

Can GF 102 laminate be used on any kind of vehicle graphics?

No. GF 102 is ideal for flat or very slight curves. In the cases of vehicles, it is best to use a conformable, long-term laminate that matches the specifications of the wrap (print) vinyl used. GF 100 Series laminates are meant for applications where up to one year of durability is needed. GF 100 series laminates are not meant to be stretched or to conform.
 

Will a Calendered laminate like GF 102 work on a Cast print vinyl?

No. You can apply a cast laminate to a calendered vinyl, but you should never put a calendered laminate on a cast vinyl. They must be of a similar construction so that over time they shrink at the same rate to avoid delamination.
// 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