null Skip to main content

GF 365 Economy - 3.0 mil gloss white vinyl

$49.95 - $149.95
Financing Options:
GF 365 Economy - 3.0 mil gloss white vinyl

GF 365 is a 3.0 mil gloss white vinyl with a clear acrylic pressure sensitive adhesive on a 75# 2-sided poly-coated layflat liner. This calendered vinyl is designed to accept a variety of solvent, eco solvent, latex and UV curable inks common to wide format digital printing systems. The adhesive produces permanent bonds to a variety of common substrates used in graphic applications short term. Engineered for general signage, window graphics, and decals, GF Economy Solutions deliver the perfect balance of quality, performance, and affordability.

 

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

 

What applications is GF 365 intended for?
GF 365 is designed for short-term interior or exterior signage, decals, nameplates, point-of-purchase displays and general signage. This product is not intended for vehicle applications.
Can GF 365 be removed?

Most decals can be removed with some effort, even if they have a permanent adhesive. GF 365 has a standard permanent adhesive that works on a variety of surfaces. This adhesive is permanent and will not remove cleanly, but any adhesive transfer or residue can be cleaned up easily with standard adhesive removers.

Free Local Delivery
Next Day Delivery
Order By 5PM CST
Save 2% On Pickup
Low Rate Financing
Flat Rate Shipping
Join Our Mailing List

Sign up to receive updates, special offers, and discounts!

// 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